Unlocking Backstage's potential: insights and solutions for a smoother developer experience
summary
Backstage is shown working as an orchestrator: teams build software templates that generate repos and create YAML-registered components, then custom actions perform tasks like creating PRs with auto‑merge. The system model is extended to allow multiple owners via YAML/Azure Entra groups, and Azure DevOps integration surfaces pipeline status. Deployment uses a monolithic multi‑stage container (build takes a few minutes). Security uses dual identity providers with resolvers and the permission system; testing relies on Jest/RTL, contract tests, end‑to‑end suites and synthetic monitoring.
AI-written summary · about
chapters (8)
- 0:00Introduction to Backstage
- 3:05Speaker introductions
- 6:16System modeling customization
- 14:33Self-service orchestration
- 23:04Deployment architectures
- 28:28Security and threat models
- 33:41Testing strategies
- 38:18Final takeaways
related talks
35mBackstage: Restoring Order To Your Chaos
28mHow Did Backstage Make 500+ Developers Happy in a Highly Regulated Enterprise
27mIntroduction to Backstage
35mImproving Developer Experience with Open Source 1
22mUnlocking Backstage’s Potential: Driving Adoption and Maturity With Your Develope...
47mImproving Developer Experience with Backstage
29mHow We Made Backstage Improve Developer Efficiency of 1000+ En...
28mBuilding Open Developer Platforms with Backstage