leader
The one replica that accepts writes and decides their order, which followers then copy.
In more detail
Having one leader makes write ordering simple and explicit. Reads that must see the latest write, such as buying a ticket, go to the leader. After a failure a follower is promoted, and the old leader must be fenced first.
Related terms
- follower — A replica that copies a partition's records from its leader and can take over if the leader fails.
- failover — Switching work from a failed or unavailable system to a standby copy so the service keeps running.
- leader election — The process by which the members of a distributed system choose one of themselves to act as leader.
- fencing — Cutting a failed or doubtful member of a replicated system off from its data so it cannot keep writing while you recover.
Taught in
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- Worked Design One: Ticket Booking, Correctness First — Scalable System Design & Distributed Architecture
- Worked Design One: Scaling The Ticket Booking System — Scalable System Design & Distributed Architecture
- Worked Design Two: Scaling Chat Fan Out — Scalable System Design & Distributed Architecture