Rolling-out like a Rock-Star
summary
Spotify replaces an old global system with an in-house remote‑config and experimentation platform that delivers >1,000 daily feature flags across Android, iOS and C++ code, built around properties.yaml defined in code and a gradle codegen → properties class + Dagger module workflow. CI publishes flags to a remote‑config admin, data scientists use Backstage to configure experiments, and a resolver serves user‑specific values with activate + fetch with cached activation and periodic background fetches. Framework enforces boolean/enum/int only, strong immutability, and supports rollouts, kill‑switches and wipes to avoid crashes and long propagation delays.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:24describe our sdk and framework in a couple of words
- 10:10create a properties yaml file
- 17:50run ci checks to validate
- 23:55cover every entry point
related talks
06mDeploying rapidly for continuous integration
01h 15mExperimentation at scale: Fuel your application’s growth through A/B testing
27mFlag Management Techniques That Support Development of Massive Apps
59mMastering Feature Flags: Best Practices with Firebase Remote Config
18mScaling Configs for Dynamic Mobile Apps
25mSet Your Developers Free: Fleet Management at Spotify
27mShifting Spotify Engineering from Spreadsheets to Backstage
59mFaster & less risky releases with feature flags