For a Spring Boot service, rendezvous hashing gives repeatable routing for the same tenant, cache lookup, account id, or request name without storing a routing table for every request. The service scores every available node for the incoming name, picks the node with the highest score, and repeats that same calculation on the next request. That gives the route a stable destination with very little shared state. Rendezvous hashing fits tenant routing, cache routing, shard selection, and any request flow where the incoming value already has a name that can be hashed.
Substack is the home for great culture