Backstage Plugin Development: Tales from the Trenches
summary
Built two plugins for CI/CD and feature flags that run as npm packages and install with a single CLI command, with the fastest prototype taking six hours. Plugins call many platform APIs so performance bugs appear under production load; a proxy for external APIs handles CORS and auth. Templates create repos and resources from templates as YAML source of truth so teams keep metadata updated. Backstage isolates crashes via composability and the open Harness Backstage Plugin ecosystem.
AI-written summary · about
chapters (10)
- 0:00Backstage and developer portals
- 3:28Why companies adopt Backstage
- 7:19Simplifying workflows with templates
- 10:27Backstage architecture and plugins
- 14:01Real-world Backstage demo
- 16:30What is a plugin
- 18:36Plugin types and roles
- 19:59Plugin development challenges
- 21:44Open-source plugins and resources
- 22:06Q&A on syncing services
related talks
34mPanel: Building a Healthy Backstage Plugins Ecosystem
08mLightning Talk: Maximising Developer Experience with Backstage: An Exploratio...
27mBuilding an Internal Developer Platform with Backstage Plugins
31mForget Rebuilding, Install Plugins at Runtime
35mBackstage: Restoring Order To Your Chaos
11mBackstage Plugins Made Simple: No Rebuild Needed
47mImproving Developer Experience with Backstage
19mBackstage Plugins: Another way to communicate your data