Zalando replaced shared edge routing for high-fan-out internal calls with an in-process load balancer that mirrors Skipper’s consistent-hash ring. They built a standalone JVM module for hash-parity routing, switched to a watch-based Kubernetes informer, and overhauled their CI/CD pipeline to safely roll out traffic ramps. The change cut latency spikes, reduced costs, and boosted deployment velocity.