A Spotify Success Story: The Migration of the Web Proxy Layer to Env...
summary
Spotify replaces an nginx‑based web proxy with Envoy, moving the Web Enrichment Platform (routing + enrichment + Concierge orchestrator) to Envoy plugins (Lua, WASM, native) and dynamic xDS config. Edge handles 6–10 million RPS overall while web traffic is ~1%; migration is 90% migrated with zero downtime using cohort rollouts, traffic splitting and dashboards. Pain points: client IP rate‑limit key missing in Envoy leading to a rethink of rate‑limiting, custom Lua kept for error/redirect behavior, file serving moved to GCS proxy.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:24Infrastructure perimeter overview
- 4:11Web enrichment platform origin
- 5:15Web enrichment platform architecture
- 9:29Configuration layer role
- 11:15Motivation for Envoy
- 13:00Engineering changes during migration
- 16:30Challenges with Envoy
- 19:20Migration process and zero-downtime
- 20:49Future platform plans
- 22:58Q&A
related talks
34mThe Spotify Story: Moving from NIH to an Active CNCF Community Member
29mThe rise of Layer 7, microservices, and the proxy war...
33mRunning Envoy as an Edge Proxy
22mUnlock Kubernetes & Envoy: Master Your API Ecosystem!
33mUsing Envoy for data aware traffic routing in Azure Service Fabric
28mExtending Envoy for Our Use: An End User Adoption Story from Fidelity
26mBuilding Multi-Tenant Routing And Scaling With Envoy
20mBuilding an Edge Control Plane with Kubernetes and Envoy