Designing Data-Intensive Applications

A field manual for the architectural decisions behind data systems: replication, partitioning, consistency models, batch vs stream, and the trade-offs nobody warns you about until production.

Every senior engineer eventually hits the limits of "just use a database." Kleppmann gives you a vocabulary to think with: eventual consistency, hot partitions, the distributed-systems pain you can't avoid. Skip the cargo-cult. Learn the trade-offs.

1. 01Reliability, scalability, maintainability: pick which one your system is actually optimizing for, then defend the choice.