NOTE
4.6 Distributed-System Replication Architecture
1. What It Is - Replicas generally have two roles: Leader, responsible for handling client write requests; Follower, synchronizes data from the Leader and can handle client read requests. 2. Categories 2.1. Leader-Follower. 2.2. Leader-Leader. 2.3. Leaderless.
This is a historical learning note and may contain outdated or incomplete understanding.
1. What It Is
- Replicas generally have two roles:
- Leader: responsible for handling client write requests.
- Follower: synchronizes data from the Leader and can handle client read requests.
2. Categories
2.1. Leader-Follower
Distributed-System Replication Architecture: Leader-Follower Replication
2.2. Leader-Leader
Distributed-System Replication Architecture: Leader-Leader Replication
2.3. Leaderless
Distributed-System Replication Architecture: Leaderless Replication
3. Examples
- MySQL supports Leader-Follower and Leader-Leader.
- Redis supports Leader-Follower.
- Kafka supports Leader-Follower.
- ZooKeeper uses Leader-Follower.
- Elasticsearch uses Leader-Follower.
Discussion
Sign in with GitHub to comment. Discussions are stored as GitHub Issues.View on GitHub