4 ms·
The author wrote a follow up about how he thinks you should build things without using a relational database: https://codeburst.io/doing-without-databases-in-th
by rgbrenner 8y ago
The author wrote a follow up about how he thinks you should build things without using a relational database: https://codeburst.io/doing-without-databases-in-the-21st-century-6e25cf495373 https://codeburst.io/doing-without-databases-in-the-21st-cen...
I think he should rename his book Creating IT Disasters
- rurban 8y agoExactly. He only knows about the advantages of persistence layers, i.e. serializing objects. But he doesn't talk about the problems of serializing pointers (refs), or even graphs (pointers upwards or to siblings). A relational structure avoids that, and so you avoid this mess. A OO store or Graph DB can handle that but is an order of magnitude slower because it has to serialize pointers, usually by checking against internal hashes or converting to arrays. Such a store is very nice to use for noobs, but once you understand the complexity of writing to such a store, you happily fall back to design a simpler scheme, which is optimized for fast reading and writing.
- pluto9 8y agoWhat he describes there amounts to a naive, lobotomized form of event sourcing.