Divide & Collaborate: Creating Scalable and Healthy Backstage Ba...
summary
ING uses Backstage to replace 60 plus internal portals with a single entry mandated by the Technology Standards Board and supports 15,000 developers across 60,000 employees. They split Backstage into multiple instances with separate databases to isolate failures and scale the software catalog with hundreds of thousands of entities. They build a golden path plugin to chain team owned templates across domains, a contribution plugin for transparent governed ideas, provide playgrounds and easy local setup, and publish the plugins at github.com/ingg-bank.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:07ING’s devx challenges
- 3:12Our Backstage journey
- 4:16Why Backstage at ING
- 6:27Convincing engineers
- 8:15Technology Standards Board
- 9:44Backstage as single entry
- 11:07Scaling without chaos
- 12:08Split architecture at ING
- 14:39Complex user journeys
- 15:44Golden Path plugin
- 18:10Governing contributions
- 19:34Contribution plugin process
- 20:38Open-sourcing plugins
- 21:02Q&A
related talks
28mHow Did Backstage Make 500+ Developers Happy in a Highly Regulated Enterprise
06mScaling Enterprise Platform Engineering with Backstage
35mImproving Developer Experience with Backstage
49mA Front Row Seat to Backstage Adoption
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
28mIDPs For The Rest of Us: Maximizing Impact When You Aren't a Tech Giant
25mLet’s Go Backstage: End to End IDP Tips & Tricks for Platform Engineers
35mImproving Developer Experience with Open Source 1