Course contentsShow
← System Design
Lesson 1368 of 1,91934. Data Replication StrategiesFree lesson

Multi-Leader Conflict Scenarios

Concurrent writes to different leaders create conflicts requiring detection and resolution strategies.

Multi-Leader Conflict Scenarios

What you'll learn: How concurrent writes to multiple leaders create conflicts that require detection and resolution strategies.

The Problem with Multiple Leaders

In multi-leader replication (lesson 1367), you gain write availability and reduced latency by accepting writes at multiple data centers simultaneously. But there's a catch: when two leaders accept conflicting writes to the same data at nearly the same time, you face a conflict that must be resolved.

Common Conflict Scenarios

Concurrent Updates to the Same Record

Two users update the same document at different leaders:

  • Leader A: User 1 changes title from "Draft" to "Final Report"
  • Leader B: User 2 changes title from "Draft" to "Q4 Summary"

Both changes succeed locally, then replicate. Which title wins?

Delete-Update Conflicts

  • Leader A: User deletes a record
  • Leader B: User updates the same record

When these operations replicate, does the record exist or not?

Uniqueness Violations

Two leaders accept new users with the same username or email simultaneously. Both succeed locally, violating the uniqueness constraint globally.

Why This Matters

Unlike single-leader systems (lesson 1365) where one leader serializes all writes, multi-leader setups allow true concurrency. The system must detect these conflicts (often after they occur) and apply resolution strategies—like last-write-wins, version vectors, or application-specific merge logic.

Without proper conflict handling, data can become inconsistent across replicas, leading to lost updates or corrupted state.

Key Takeaway: Multi-leader replication trades write simplicity for availability—concurrent writes create conflicts that require explicit detection and resolution mechanisms to maintain data integrity.