Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- Explain why multi-leader replication exists, and what problem it solves that single-leader cannot.
- Define a write conflict concretely, with a worked example.
- Describe at least two conflict resolution strategies.
- Decide whether multi-leader replication fits a given scenario, weighing its benefit against its conflict risk.
The previous two pages assumed exactly one leader accepting all writes. This page covers what happens when that single-point-of-write restriction itself becomes the problem. It also covers what a database gives up to remove it.