Quorum-Based Systems
What you'll learn: How distributed systems use majority voting to make safe decisions and prevent catastrophic split-brain scenarios.
The Core Idea
After learning about the split-brain problem (where two parts of a system both think they're in charge), quorum-based systems offer an elegant solution: require a majority vote before taking any critical action. Instead of letting any single node or minority group make decisions independently, the system enforces that more than half of the nodes must agree.
Think of it like a board of directors requiring a majority vote to approve major decisions—no single director can act alone, and if the board splits into two isolated groups during a network partition, only the group with the majority can continue making binding decisions.
How It Works
In a quorum system with N nodes, you need at least (N/2) + 1 nodes to agree before committing writes or electing a leader. For example:
- 3 nodes → need 2 to agree
- 5 nodes → need 3 to agree
- 7 nodes → need 4 to agree
This mathematical guarantee ensures that two quorums always overlap—you can never have two separate majorities making conflicting decisions. If a network partition splits your 5-node cluster into groups of 2 and 3, only the group of 3 can form a quorum and continue operating. The group of 2 knows it lacks quorum and stays read-only or refuses writes entirely.
Why Odd Numbers?
Systems typically use odd numbers of nodes (3, 5, 7) because it maximizes fault tolerance without wasting resources. With 4 nodes, you still need 3 for quorum—same as with 5 nodes, but less redundancy.
Key Takeaway: Quorum-based consensus requires majority agreement for critical operations, mathematically preventing split-brain by ensuring only one group can ever hold a majority, making distributed decisions safe and consistent.