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 & architecture questions
- What does CodeDeploy RESTART actually deploy?
- Does CodeDeploy RESTART work with ECS or Lambda?
- Does RESTART remove an application from load-balancer traffic while it restarts?
- Does Elastic Beanstalk's Active Directory join require a domain password?
- Can an Elastic Beanstalk environment be healthy if the domain join fails?
- Will enabling Active Directory replace running instances?
- What is different about AWS Lambda Web Functions?
- Does Lambda Web Functions automatically cost less than ordinary Lambda?
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 & Architecture beat.