Driving Monorepo Adoption With Backstage
summary
Company runs a monorepo on AWS and Kubernetes with Bazel, CDK and Terraform/OpenTofu, and faces migrating hundreds of existing apps. Backstage powers Backstage Software Templates that generate a PR, an ArgoCD AppSet and deploy CRD/operator resources so a new app reaches a dev URL in ~7 minutes (goal: 10 minutes). Integrations include Grafana + Prometheus alerting as code, PagerDuty + Slack on-call creation, and a Software Catalog + custom plugins to visualize ownership and dependencies.
AI-written summary · about
chapters (12)
- 0:00Monorepo and Backstage intro
- 1:04Zipline’s mission and growth
- 3:33Why monorepo strategy
- 4:58Monorepo tech stack
- 9:16Monorepo adoption challenges
- 13:11Onboarding with Backstage
- 15:18Backstage implementation
- 18:30Internal dev portal
- 20:16Demo: app template creation
- 22:44Lock-in features for adoption
- 24:10Alerts as infrastructure
- 26:39Summary and future
related talks
41mHandling Monorepos Today
01h 03mMonorepo – How to do frontend faster, better and safer
01h 00mFOUR PILLARS AND A BASE: THE NUTS AND BOLTS OF A MONOREPO
01h 00mUsing Monorepos for Scalable Apps
19mKeynote: Why Monorepos
24mBeyond Review Apps: Orchestrating Full-Stack Ephemeral Environments...
23mMonorepos & Spaceships - Navigating successfully through Code and Cosmos
46mExploring the power of monorepos: When and why to use them