> Yeah, no shit, it's hard to get things like referential integrity and transactions working at scale, it takes many genius engineers and many years.
Well, the problem is that such mechanisms _must_ be in place (in well-designed applications); they're not optional.
The consequence is that, if they're not implemented at the lower (db) layer, then they're going to be implemented at the higher (app) layer.
There is often the discussion of indexing/referential integrity for schemaless data stores. One may think that such data stores solve those problems; they don't - they push it to the application.
Therefore, it takes many genius engineers-years... anyway. Solutions provided by the data stores, like FKs, just happen to solve the problem out of the box (where applicable, which of course, it's not always the case).
The article actually mentions this, although not so dramatically :-)
Well, the problem is that such mechanisms _must_ be in place (in well-designed applications); they're not optional.
The consequence is that, if they're not implemented at the lower (db) layer, then they're going to be implemented at the higher (app) layer.
There is often the discussion of indexing/referential integrity for schemaless data stores. One may think that such data stores solve those problems; they don't - they push it to the application.
Therefore, it takes many genius engineers-years... anyway. Solutions provided by the data stores, like FKs, just happen to solve the problem out of the box (where applicable, which of course, it's not always the case).
The article actually mentions this, although not so dramatically :-)