Modern HTTP routing should support traffic switching, provide fine granular visibility, add resiliency patterns, be extensible, and should be easily configured by development teams. At Zalando SE, we run more than 80 Kubernetes clusters and developed open source tools to support the mentioned features. One core component, skipper, we internally call the swiss army knife of HTTP. It provides filters to modify HTTP data, headers, and body. It allows us to specify route matching with predicates. Using these principles we can support deployment patterns like blue-green, shadow traffic, or A/B tests.
Shadow traffic is one less known feature that enables users to test new architecture with production traffic, without disrupting production.
Modern l7 software load balancers have to be simple to scale, provide visibility in depth, and enhance resiliency. Retries, circuit breaker, or rate limits are interesting cases that can support your applications being more resilient to failure. How to do rate limits in a growing and shrinking cluster, that means changing number of replicas in the backend and also load balancer instances?
The talk will show a modern HTTP router and it's features and show some practical use cases from our production setup that can be reused by the audience.
