Client‑Side Load Balancer Powers Over 1 M RPS, Slashing Latency and Costs
Zalando’s team rewrote internal routing for its Product Read API with a pure client‑side load balancer that now sustains over a million requests per second. By pulling routing decisions out of Skipper and adding N‑ring fade‑in, occupancy‑based load limits and AZ‑aware latency health, they cut latency, lowered cost and hardened the service against infrastructure failures.