Book · 2017
Designing Data-Intensive Applications
by Martin Kleppmann
Martin Kleppmann walks backend engineers through every database, queue, and consistency tradeoff they'll eventually get paged about.
Catalogue record: Open Library
What does Reddit think of Designing Data-Intensive Applications?
'As a backend engineer, this is your bible' — that line, from a ↑349 r/ExperiencedDevs comment, keeps getting cited, and the rest of the data backs it up rather than undercutting it. r/ExperiencedDevs supplies about half of DDIA's 436 recognized mentions and the warmest sentiment of any subreddit tracked. A ↑236 comment gets specific about the mechanism: it gave the poster a common language for architecture conversations with senior engineers, then became a reference they returned to once actual production problems showed up, not just a book they finished once. Even the tangents draw engagement: a ↑265 thread about Kleppmann's own disclosed royalties, 477k over three and a half years, generated real discussion on its own. Mentions peaked in 2022 at 94 and have eased since, though nineteen already in early 2026 suggest it hasn't dropped off so much as leveled out.
Evidence, not a rating
Recommendation receipt
A compact, source-linked answer derived from the same Reddit sample and editorial synthesis as this page.
Editorial summary
'As a backend engineer, this is your bible' — that line, from a ↑349 r/ExperiencedDevs comment, keeps getting cited, and the rest of the data backs it up rather than undercutting it. r/ExperiencedDevs supplies about half of DDIA's 436 recognized mentions and the warmest sentiment of any subreddit tracked.
Read if
You keep losing arguments about replication lag or partition strategy and want the vocabulary to hold your own. That's the exact use case in the ↑236 r/ExperiencedDevs comment. Come to it after you've been paged for something breaking under load, not before; the 'your bible' framing at ↑349 comes from engineers already doing the job, not people studying for one.
Skip or borrow first if
r/cscareerquestions mentions it 124 times at flat sentiment — present on lists, not treated with the weight r/ExperiencedDevs gives it.
Strongest published evidence
“We should really just put together a community reading/listening list... Reading: * Clean Code / Clean Architecture / […”r/cscareerquestions source · score 498 ↗
Dissent & strongest caveat
r/cscareerquestions mentions it 124 times at flat sentiment — present on lists, not treated with the weight r/ExperiencedDevs gives it.
Community feedback & reader fit
Themes
- · Distributed systems tradeoffs made explicit
- · Database internals: replication and consistency models
- · Batch and stream processing as a unified topic
- · Shared architecture vocabulary across a team
- · A reference revisited once real incidents happen
Common praise
- + A ↑349 r/ExperiencedDevs comment calls it 'your bible' for backend engineers, no qualifiers attached.
- + A ↑236 commenter credits it with giving them a common language for architecture conversations with more senior engineers, not just abstract knowledge.
- + Gets treated as a reference to return to once a real production problem hits, per that same ↑236 thread, rather than a one-and-done read.
- + Even the author's own economics became a discussion topic (↑265) — a sign of a fanbase invested enough to track royalty disclosures.
Common criticism
- − r/cscareerquestions mentions it 124 times at flat sentiment — present on lists, not treated with the weight r/ExperiencedDevs gives it.
- − Yearly mentions peaked at 94 in 2022 and have declined most years since, down to 54 in 2025.
- − The book shows up thin in adjacent fields, 14 mentions in r/datascience, 5 in r/MachineLearning, so its audience stays fairly narrow to backend engineering specifically.
- − Nothing in the visible sample pushes back on the content directly; the closest thing to friction is just some subreddits rating it lower-stakes than others.
Who it's for
You keep losing arguments about replication lag or partition strategy and want the vocabulary to hold your own. That's the exact use case in the ↑236 r/ExperiencedDevs comment. Come to it after you've been paged for something breaking under load, not before; the 'your bible' framing at ↑349 comes from engineers already doing the job, not people studying for one. Data scientists and ML engineers show up in the mention count too, just barely, 14 and 5 respectively, on the radar without being central to it.
Mentions over time
Which Reddit comments matter for Designing Data-Intensive Applications?
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. Click through to read the full thread.
“We should really just put together a community reading/listening list... Reading: * Clean Code / Clean Architecture / […
“Read Designing Data-Intensive Applications by Martin Kleppmann. As a backend engineer, this is your bible.
“Lol there was just a thread about this in the ExperiencedDevs sub TL DR of the thread 1. Systems Expert (by the AlgoExpert guy) is too basic and not worth the $100. 2. Read tech blogs. There's a free newsletter that sends out summaries of tech blogs (they also send leetcode…
“Designing Data-Intensive Applications.
“Designing data-intensive applications by Martin Kleppman was eye opening for me because it gave me a common "language" in order to speak with other experienced engineers about high level architecture. It also is just incredibly useful as a reference when you actually start to run into problems wher…
“Designing Data Intensive Applications is phenomenal
“If you really want an in-depth grasp of databases, I can highly recommend ‘Designing Data-Intensive Applications’ by Martin Kleppmann
“Designing Data-Intensive Applications by Kleppmann is the current hotness.
“Designing Data Intensive Applications gets checks off quite a few on your list there.
“It’s a long story. Distributed computing is hard. Lots of people (myself included) recommend Designing Data Intensive Applications book.
“Designing Data Intensive Applications by Martin Kleppmann Fluent Python if you’re a python programmer. I’m gonna just call Knuth / SICP / Clean Code / Design Patterns out as doorstops people never actually read.
““Designing Data Intensive Applications” is fantastic if you haven’t read it yet and have an interest in distributed systems.
“I would say that this is exactly it, a decent survey of the backend landscape, which is already a lot. A university-level course like that from Tanenbaum and van Steen is hardly a digestible source for beginners, whereas most interview-level guides are either extremely inaccurate or too shallow. Tha…
“Designing Data Intensive Applications is a must read.
“Some books can be consumed in audiobook form, which can be done while doing chores, e.g. washing dishes, or while driving. This is the primary way I have time for books. Here are some good ones: * Pragmatic Programmer (2nd edition) * Designing Data-Intensive Applications * Meltdown: Why Our Sys…
Convinced? Pick up Designing Data-Intensive Applications
Readers also mention
Books that share discussion threads with Designing Data-Intensive Applications — counted from the comments, not curated.
Guides featuring Designing Data-Intensive Applications
Ranked best-of lists and editorial guides where this book's tracked mentions place it.
Designing Data-Intensive Applications — frequently asked
What does Reddit think of Designing Data-Intensive Applications?+
Strongly positive, especially among engineers already doing the work. r/ExperiencedDevs supplies about half the mention volume and the warmest sentiment in the dataset, anchored by a ↑349 comment calling it a backend engineer's 'bible.' r/cscareerquestions engages with it too, just at a flatter, more list-like register.
Is Designing Data-Intensive Applications still worth reading in 2026?+
Yes, per the mention pattern. It peaked in 2022 at 94 yearly mentions and has cooled since, but nineteen mentions already showed up in early 2026, and r/ExperiencedDevs was still citing it in March. The tradeoffs it covers change slower than the specific tools implementing them.
Is Designing Data-Intensive Applications only for people already building distributed systems?+
No — a ↑236 r/ExperiencedDevs comment specifically credits it with giving them shared vocabulary for talking to people who do build distributed systems, even without building one personally. That said, mention volume outside backend-focused subs stays thin: 14 in r/datascience, 5 in r/MachineLearning.
Why do people call Designing Data-Intensive Applications a 'bible' for backend engineers?+
That's a direct quote, from a ↑349 r/ExperiencedDevs comment, not editorial framing. A separate ↑236 comment explains the mechanism: it works as both an initial education and a returnable reference once specific production problems show up down the line.