Keynote: 4 Common Pitfalls to Avoid When Onboarding Backstage
summary
Backstage adoption surfaces four clear pitfalls: four pitfalls are that Backstage is a framework requiring TypeScript development so teams often must hire devs — you build it, you own it — it needs production ops (Docker images, Kubernetes, Helm or kustomize, Argo CD, availability/scale planning), plugins require code edits and rebuilds despite ~100 community plugins — plugins aren't really plugins — and success depends on adoption metrics and integrating catalogs/workflows with existing CI/CD and communication channels.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03About Backstage
- 2:48Platform engineering basics
- 3:53Building an IDP
- 5:40Common onboarding pitfalls
- 6:24Pitfall one: Backstage as a development project
- 7:51Pitfall: Production deployment
- 9:13Pitfall: Plugin management
- 10:18Pitfall: Developer adoption
- 11:20Summary
- 12:24Q&A
related talks
36m4 Common Pitfalls when Adopting Backstage
32mIs Backstage for me?
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
04mKeynote: 10x the Effectiveness of Dev Teams with Backstage
12mKeynote: Providing a Curated Experience for Developers with Backstage
31mBackstage Adoption Deep Dive - Navigating the Pitfalls
49mA Front Row Seat to Backstage Adoption
27mLessons from a Year with Backstage: What Worked, What Didn’t...