Value Driven Platform Engineering Using Backstage
summary
States that 24.3M active devs exist and US firms spend $165B while developers spend 40% of their time on non-code work, costing roughly $1T; Backstage acts as an open IDP with a user-aware catalog, relationship graph, logs and dashboards that cut onboarding from ~60 days to 20 days onboarding at Spotify and improves MTTR by surfacing owners and data. Deployments use plugins—Spotify has 135 plugins, harness has ~40 and built three—and notes that self-managed deployment is hard with uptime and security critical.
AI-written summary · about
chapters (11)
- 0:00Platform engineering with Backstage
- 1:13Developer productivity challenges
- 2:36Backstage trends and adoption
- 3:40What Backstage solves
- 4:42Backstage impact on metrics
- 5:46User context in Backstage
- 7:12Backstage plugins and integrations
- 8:36Developer adoption strategies
- 9:19Optimizing Backstage usage
- 10:20Self-managing Backstage challenges
- 11:04Conclusion
related talks
26mBackstage: Shaping the Future Of Developer Experience
41mBackstage.io: Spotify's platform developer experience
35mImproving Developer Experience with Backstage
47mImproving Developer Experience with Backstage
05mThe Future is Backstage: Building a Better Platform from...
42mNavigating Backstage: A Year in Developer Life
28mIDPs For The Rest of Us: Maximizing Impact When You Aren't a Tech Giant
39mHow Spotify engineers use Backstage daily and keep their lives simple