Leading Architectural Change with Backstage
summary
A fintech that hits Series C and 10x growth describes using Backstage with a Roadie-managed instance plus scaffolder templates and Argo CD/Workflows to turn multi-week service onboarding into minutes, cutting some component setup from two months to minutes. Platform uses GitHub-driven PR workflows, Helm umbrella charts, config-connector, plans for OPA policy checks, and a custom “ANTLERS” scaffolding layer; result is consistent naming, audit trails, fewer operational tickets, and faster safe rollout of microservices.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:27Backstory
- 5:02Caribou Culture
- 6:38Challenges
- 8:37A Lost Opportunity
- 9:52Reasons Not to Change
- 13:33Design for Scaffolder
- 16:29Simplicity - Intuition
- 17:37Management Plane
- 19:50Resource Taxonomy
- 22:01Helm + Scaffolder
- 23:21The Result
- 25:55Modular Components
- 26:31Tech Rader
- 27:18Why Change is Hard
- 29:12Leading Architectural Change with Backstage
related talks
11mLightning Talk: The Backstage Builder Experience at Adyen
27mIntroduction to Backstage
06mHow to Succeed with Backstage
32mIs Backstage for me?
28mHow Did Backstage Make 500+ Developers Happy in a Highly Regulated Enterprise
47mImproving Developer Experience with Backstage
35mImproving Developer Experience with Open Source 1
35mBackstage: Restoring Order To Your Chaos