Scaling Edge Operations at Onefootball with Ambassador: From 0 to 6000 rps
summary
Onefootball moves from many per-service ELBs to a single Ambassador-based ingress, driving reduced ELBs from >100 to 4 and saving about $20k/year, while serving spikes up to 6,000 rps for a 10M MAU app. Migration uses Helm chart artifacts, a shared helm-chart repo, Route53 gradual rollouts (1–10% then to 100%), and Ambassador features like traffic shadowing and header/path-based canaries. Metrics flow via statsd exporter → Prometheus; tracing exports to Zipkin.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:33World Cup Hangover effect
- 7:25Finding an Ingress solution
- 22:02Ambassador metrics
- 23:53New features release
related talks
33mRunning Envoy as an Edge Proxy
36mHow Spotify Migrated Ingress HTTP Systems to Envoy
24mHow Spotify Migrated Ingress HTTP Systems to Envoy
15mFrom ingress-nginx to Envoy Gateway at Zapier: The...
37mLevel Up Your Edge: Do You Know Where Your Traffic Comes From?
36mUsing Ambassador to Build Cloud-Native Applications
14mFrom Overwhelmed to Optimized: How We Cut Envoy Logging Costs by 65% While Boosting Throughput 60%
Monitoring Cloudflare's Planet-Scale Edge Network