Paxos Made Simple

Why this one

Read this after In Search of an Understandable Consensus Algorithm. Raft gives you the engineer's shape of replicated logs, leaders, terms, and commitment. Paxos gives you the smaller, stranger core underneath: how a group can choose one value even when messages vanish, machines pause, and nobody can tell whether a peer is dead or slow. What people get wrong is treating Paxos as a protocol you copy into production. The paper is more useful as a proof-shaped mental model. It teaches you which guarantees come from quorums, which come from promises, and why the hard part is not electing a leader but preserving safety across every half-finished attempt. If you build storage, queues, schedulers, config systems, or anything that says highly available, this is an evening well spent because it changes what you distrust in your own designs.