Designing Data-Intensive Applications - dry, despite the reputation

I picked this one up because it’s so highly rated. Everyone seems to rave about it, so I figured I should see what the fuss was about.

I found this one really dry and it spent ages focusing on details I didn’t find useful. A lot of the in-depth database internals stuff was just too specific for me. It had some good information for sure, I just didn’t enjoy the way it was written and the more theoretical focus over practical applications.

I did finish it, which counts for something. But if you asked me what I’ve directly applied from it in real work, I honestly can’t point to anything. Maybe something soaked in by osmosis.

So who should read it? Maybe someone who hasn’t had to architect these systems yet and wants to know what questions to ask. As a map of the territory, it works. If you’ve already been in the trenches building and running these systems, I’d skip it.

Honestly, my alternative recommendation isn’t even a book. I’d suggest architecting some project ideas yourself and then talking through them with AI. You’ll learn the trade-offs faster by wrestling with a real design than by reading about them in the abstract.

3/5 from me. Good information, dull delivery.