4 ms·
So many recommendations for this book but I really didn't like it, very theoretical. It lists a lot of the main data related software systems and how they work,
by x87678r 6y ago
So many recommendations for this book but I really didn't like it, very theoretical. It lists a lot of the main data related software systems and how they work, but that seemed about it. I really expected comparisons and tradeoffs, eg when should you switch from using a database to a message queue to Kafka? No real world examples or design experience.
- throw_this_one 6y agoGroupthink. Just like that book about sleep and whatever other pop pseudo intellectual books are repeated on here.
- deleted 6y ago[deleted]
- aprdm 6y agoEverything is so case specific. And at the same time most of the tools work pretty well for the scale of most companies to the point they it doesn’t matter when you chose what... Because of those two I don’t know exactly what people expect apart from either specific use cases ( conferences , blogs , etc.) or generic fundamentals (the book).
- diehunde 6y agoSounds like you didn't read the book. There's actually a section with the title "Message brokers compared to databases" with a detailed comparison.
- x87678r 6y agoI can't see in the ToC https://www.oreilly.com/library/view/designing-data-intensive-applications/9781491903063/ https://www.oreilly.com/library/view/designing-data-intensiv...