Part 1 of 7 · 1 min read
Why this page comes after rebalancing
In this module you will
- State the routing question in a partitioned data store and see why it is an instance of service discovery.
- Describe the three routing designs: any node forwards, a routing tier, and a partition-aware client.
- Explain why all parties must agree on the map of partitions to nodes, and what goes wrong if they do not.
- Describe the role of a coordination service such as ZooKeeper, and the gossip alternative.
- Trace a request through a system with a config store, a gateway and shard nodes, including a partition move.
Module 5 moved partitions between nodes. Someone must now tell clients where each partition lives, and keep that knowledge current while it changes. That is the routing problem. The tier is Common. The numbers are made up to show the idea, unless the text names a book.