Spotify's Growth Exposed the Abstraction Paradox
summary
Rapid growth makes clean APIs hide crucial operational detail, causing new hires to take 60 days to 10th PR while abstractions work for 90% vs 10% of cases and fail in outages. A platform approach encodes operational wisdom via a golden path, plugin service catalog and TechDocs; the company builds Backstage, Backstage open sourced 2020 and donates it to CNCF, and sees onboarding and reliability metrics improve as deep dives become available.
AI-written summary · about
chapters (8)
- 0:00Introduction and Speaker Background
- 0:28Understanding Abstractions
- 1:25Challenges with Abstractions at Spotify
- 3:28Building Better Abstractions
- 6:48Operational Knowledge and Learning from Failures
- 8:55Implementing Effective Abstractions
- 13:01Backstage: Spotify's Open Source Solution
- 16:20Q&A Session
related talks
27mShifting Spotify Engineering from Spreadsheets to Backstage
34mThe Spotify Story: Moving from NIH to an Active CNCF Community Member
19mHigh Performance Backstage for High Performing Organizations
27mBalancing autonomy, technical alignment, & speed through strategic collaboration
25mPlatform Engineering: Evolution or a Fancy Rename?
05mThe Future is Backstage: Building a better platform from the...
23mScaling the Sound: Fleet Management at Spotify
09mSelf-Service Infrastructure