Archivedistributed-systems
Paxos vs Raft: Same Guarantees, Different Ergonomics
Paxos is a family of protocols; Raft is a specification with an implementation manual. Choose by ecosystem, not theory.
- Published
- Reading time
- 1 min read
Both solve consensus in an asynchronous network with crash faults, and both need a majority quorum. The difference is how much of the design is fixed for you.
Paxos
- Single-decree Paxos decides one value; Multi-Paxos extends it to a log.
- Roles are proposer, acceptor, learner, and the protocol composes cleanly.
- The original paper is famously underspecified on practical details: leader election, log repair, membership changes.
Raft
- Built around a strong leader and a replicated log from the start.
- Specifies membership changes, snapshots, and client interaction.
- Easier to reason about and to test; more opinionated.
Practical selection
| Need | Pick |
|---|---|
| A storage system, strong ecosystem | Raft (etcd, TiKV, CockroachDB) |
| A single decision, flexible roles | Paxos |
| Byzantine faults | Neither — PBFT/HotStuff family |
Takeaway: the algorithms are close in cost. Pick the implementation with the operational tooling, membership change story, and tests you can trust.