What's the difference between single-leader and multi-leader replication?
Single-leader replication routes all writes through one designated node, which then propagates changes to replicas — simple to reason about, since there's never a question of which write wins. Multi-leader replication allows writes to more than one node, useful for multi-region setups where each region wants local write latency, but it introduces the hard problem of resolving conflicting concurrent writes to the same data.
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.