Goal
The path to "Designing Distributed Systems"
Here is the reading path leading up to this book, derived from its dependencies and ordered from the fundamentals.
The path so far (3 books)
Why read this first: A key to achieving continuous delivery is producing an artifact that 'runs the same everywhere'. Poulton's 'Docker Deep Dive' explains container-based standardization and portability from the ground up, fixing the standard form of the artifact a CD pipeline ships as a container.
Why read this first: After understanding how to build and run a single container in Poulton's 'Docker Deep Dive', the challenge in production becomes orchestrating many containers together. Lukša's 'Kubernetes in Action' explains container orchestration from the ground up, scaling you from one container to distributed operation.
Why read this first: Learning to use Kubernetes raises the design question of what distributed apps to build on top of it. By Kubernetes co-founder Brendan Burns, 'Designing Distributed Systems' presents reusable distributed patterns—replicated load-balanced services, sharding, scatter/gather—in the vocabulary of K8s.