NOTE
5.3 Distributed-System Partitioning: Routing Components
1. client - The client locally stores the relationship between partitions and server nodes and directly requests the correct node. 2. proxy - The client requests the routing layer, and the routing layer forwards the request to the correct node. 3. server - The client requests any server node, and that server node forwards the request to the correct node.
This is a historical learning note and may contain outdated or incomplete understanding.
1. client
- The client locally stores the relationship between partitions and server nodes and directly requests the correct node.
2. proxy
- The client requests the routing layer, and the routing layer forwards the request to the correct node.
3. server
- The client requests any server node, and that server node forwards the request to the correct node.
4. Examples
- MySQL uses proxy or client.
- Redis uses client + server.
- Kafka uses client + server.
- ZooKeeper does not use partitioning.
- Elasticsearch uses server.
Discussion
Sign in with GitHub to comment. Discussions are stored as GitHub Issues.View on GitHub