Why would a system choose leaderless replication over single-leader?
Leaderless replication (no single node designated as authoritative) avoids the single point of failure a leader represents and tolerates individual node failures gracefully, using techniques like quorum reads/writes and read repair to stay consistent. The trade-off is more complexity in the client or coordination layer, since there's no single node to ask 'what's the current value' with full confidence.
Answered in
Database Replication Explained: Single-Leader, Multi-Leader, and LeaderlessWhat replication lag actually breaks, and how single-leader, multi-leader, and leaderless models trade off consistency for availability.
Read the full analysisOther questions this article answers
More system design questions
- Why does a database need an index at all — why can't it just scan the table?
- When is a hash index better than a B-tree index?
- What is a composite index and why does column order matter?
- What's a covering index and why is it faster than a normal index?
- What's the real cost of adding an index, beyond disk space?
- What does ACID actually stand for, and why do all four properties matter together?
- What's the practical difference between pessimistic and optimistic concurrency control?
- What is a race condition in a database transaction, and how does isolation prevent it?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design beat.