Breaking the (developer) silos

on YouTube ↗11m

" summary

Spotify replaces its old ABA feature-flagging system by building a new experimentation platform centered on remote configuration that exposes reusable properties so mobile releases no longer stall experiments. A cross-disciplinary team of backend, data, web and mobile engineers sketches common abstractions (sessions, APIs), iterates for platform-specific constraints, and ships after about one year of work. Result: clearer separation of concerns, idiomatic client/server solutions, and fewer cross-platform assumptions — not a fit for every infra problem.

AI-written summary · about

" chapters (8)

1. 0:00Intro
2. 0:33Questions
3. 1:15Spotify example
4. 3:14Common abstractions
5. 5:05Learning sharing
6. 5:55Reusable features
7. 7:01Trust
8. 8:45Diverse teams

" related talks

• 47mDeath Of The "Spotify Model"Marcin Pakulnicki, Gijs Meijer · GOTO Amsterdam 2022
• 49mMicroservices at SpotifyKevin Goldsmith · GOTO Berlin 2015
• 52mHow do we do product at SpotifyRachel Dubois · Agile on the Beach 2024
• 29mThe Spotify model - Does copy paste implementation workVili Mileva Yankova · DevOpsDays Eindhoven 2022
• 43mThe #Spotify model - Does copy/past implementation work?Vili Mileva Yankova · Update Conference Prague 2022
• 46mScaling Agile in your Organization with the Spotify ModelStephen Haunts · NDC Oslo 2017
• 39mOwn your speedPia Nilsson · Øredev 2019
• 48mAgile at scale at SpotifyJoakim Sunden · Wildcard Conference 2013