Roadmaps / Distributed Systems
Foundations · 16 study weeks · 4 phases
Distributed Systems Roadmap Beta
A distributed system fails in ways a single machine never does. Clocks disagree, messages arrive late or twice, and a node can look dead while it is still working. These 16 study weeks teach time and failure, replication and consensus, storage and scale, and how to test a system the way its failures will test it. You build one system, quorumkv, a replicated key-value store, and every phase adds a checkpoint to it. At 8 hours a week the core path is 128 hours and takes 16 weeks. At 12 hours a week it takes about 11 weeks, and at 16 hours a week about 8 weeks. At the end you can show, with a checker and not with a claim, what your system guarantees when nodes crash and the network splits.
This roadmap is in beta and keeps improving over time. If you spot an error, please email your suggestions and corrections to [email protected].
Read first
Phase 1 · Study weeks 1-4
Time, failure and messages
This phase makes the first checkpoint possible: nodes that notice failure and handle repeated or late messages safely.
- 3 repos
- Milestone checkpoint
- Study week 1System models: crash, omission and Byzantine faults8 h
- Study week 2Time and order: physical clocks, skew and drift8 h
- Study week 3Failure detection with heartbeats8 h
- Study week 4Broadcast and dissemination8 h
Phase 2 · Study weeks 5-8
Replication and consensus
This phase makes the second checkpoint possible: a replicated log that elects a leader and never loses an acknowledged write. It is four weeks because consensus is hard to get right.
- 4 repos
- Milestone checkpoint
- Study week 5Replication styles: leader-based, multi-leader and leaderless8 h
- Study week 6Leader election8 h
- Study week 7Log replication8 h
- Study week 8Linearizability and how a checker tests it8 h
Phase 3 · Study weeks 9-12
Storage, reads and scale
This phase makes the third checkpoint possible: a store that survives restarts, keeps its log small and serves reads with a stated guarantee.
- 4 repos
- Milestone checkpoint
- Study week 9The write-ahead log and fsync8 h
- Study week 10Linearizable reads: through the log, read index and leases8 h
- Study week 11Storage engines: LSM trees and B-trees8 h
- Study week 12Throughput and tail latency8 h
Phase 4 · Study weeks 13-16
Testing, models and operations
This phase makes the last checkpoint possible: a system tested the way its failures will test it, with a runbook for the failures you found.
- 3 repos
- Milestone checkpoint
- Study week 13Jepsen-style testing: generators, nemeses and checkers8 h
- Study week 14Formal models with TLA+ or a model checker8 h
- Study week 15Membership changes8 h
- Study week 16Failure drills and runbooks8 h