The Spotify Story: Moving from NIH to an Active CNCF Community Member
summary
Spotify shifts from homegrown stacks to CNCF ecosystems, running on a cloud provider with 200 million monthly users and about 2,500 microservices, 8–9 million peak QPS and 220 public GitHub projects. Migration to Kubernetes and gRPC requires building a shared VPC and namespace metrics, heavy integrations for logging and data pipelines, 18 months of coordinated migration work, and a “build infrastructure together” strategy that embeds engineers with users and drives external pull requests.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:12The power of community
- 12:03Plugging things into your ecosystem is really hard
- 17:36Building in the open is hard
- 21:50We call it "Building Infrastructure Together"
- 23:59This is MORE than collaborative development
related talks
16mInside Spotify’s Envoy Architecture: What We Le...
20mSpotify's Growth Exposed the Abstraction Paradox
35mTo Infinite Scale and Beyond: Operating Kubernetes Past the Steady State
35mA Spotify Success Story: The Migration of the Web Proxy Layer to Env...
38mBuilding and Managing a Centralized Kubeflow Platform at Spotify
09mSelf-Service Infrastructure
01h 02mAutomating the component maintenance - Fleet management at Spotify
12mKeynote: Scaling Cloud Native Adoption