← Back to Labs
Load Balancing Decision Explorer
Compare L7 routing policies under hot backends, ejections, draining, and regional failover while the L4 flow stays pinned to one frontend.
Routing policyChoose how the frontend should pick a backend for this request
Affinity keySwap the key that a sticky or hashed policy would try to preserve
Chosen backend
app-a
ath-1
Observed load
28 active requests
22 ms recent latency
Why it won
Least requests prefers the backend with the lightest live occupancy after applying a small penalty for slow or cold nodes.
Step 1 / 6L4 hashing lands the flow on one frontend proxy
The public entry layer does not know paths or cookies yet. It hashes the five tuple so every packet of the same flow keeps reaching the same frontend.
app-a wins because its queue and latency footprint are the lowest among healthy non-draining nodes in this step.
Arrow keys to navigate · R to reset
Tap dots to jump to any step