Initiates value proposal
Cloud / Knowledge library
Paxos Consensus
Chooses values through proposer, acceptor, and quorum phases
Why learn Paxos Consensus?
It provides a foundational crash-fault consensus model
The problem it solves
It reaches agreement without relying on one permanently available coordinator
Where it came from
Paxos Consensus is a distributed systems concept that chooses values through proposer, acceptor, and quorum phases. Its guarantees and tradeoffs depend on the concrete implementation and operating context.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Define Paxos Consensus and distinguish it from a neighboring concept.
- Choose a realistic task where Paxos Consensus is appropriate.
- Identify a failure mode caused by misusing Paxos Consensus.
- Interpret a small design or result involving Paxos Consensus.
- Explain one tradeoff or limitation of Paxos Consensus.
Documentation and sources
- Designing Data-Intensive Applications (dataintensive.net)
Connect the ideas
Explore next
Real World Example
Global Inventory Synchronization for AeroParts
AeroParts, a global aerospace logistics provider, manages critical aircraft component inventory across three geographically dispersed data centers.
The business problem
The company faces significant data inconsistency issues when multiple regional offices attempt to update the same part availability status simultaneously, leading to overselling or phantom inventory errors.
How this topic solves it
AeroParts implements the Paxos consensus algorithm to ensure that all regional nodes agree on a single, linearizable sequence of inventory updates, preventing conflicting state changes.
- Proposer nodes broadcast a proposal with a unique sequence number to all Acceptor nodes.
- Acceptors evaluate the proposal and promise to ignore any future requests with lower sequence numbers.
- If a majority of Acceptors acknowledge the proposal, the Proposer sends an accept request for the specific value.
- Acceptors commit the value if they have not promised to a higher sequence number in the interim.
- The system confirms the update as globally consistent once a quorum of Acceptors has successfully stored the value.
The flow shows the interaction between a Proposer and a quorum of Acceptors to reach consensus.
Validates and promises
Validates and promises
Validates and promises
- Proposer → Prepare(seq) → Acceptor 1
- Proposer → Prepare(seq) → Acceptor 2
- Proposer → Prepare(seq) → Acceptor 3
- Acceptor 1 → Promise/Ack → Proposer
- Acceptor 2 → Promise/Ack → Proposer
Expected business outcome
The system achieves a reliable, single-source-of-truth for inventory levels, ensuring that no two regions can commit conflicting updates to the same component record.
Limitations and checks
Paxos introduces increased latency due to the multi-phase communication required for quorum agreement; developers can monitor this by tracking the time elapsed between proposal initiation and final commit acknowledgement.