The Evolution of Backstage Backends
summary
Backstage backend moves from per-install wiring to a framework that wires plugins, offering a single call createBackend instead of nine files and 348 lines (now ~1 file, 26 lines). It adds dependency-injected services, default service factories so plugins rarely require backend changes, and formalizes plugin extensions as modules and extension points. Migration is mostly deleting custom wiring (no DB changes), early releases are available for testing, and the design aims to cut breaking changes and simplify long-term evolution.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:01History
- 2:15A Simple Plugin
- 3:11Plugin Integration
- 3:44Headaches
- 4:18Evolving Plugins
- 8:03Building Blocks
- 11:40New System, Backend
- 12:23New System, Plugin
- 13:26Module Implementation
- 14:27Plugin Implementation
- 15:17Custom Services
- 15:50Default Service Factories
- 17:17Size Comparison
- 17:50App Migration
- 18:48Plugin Migration
- 19:26Summary
related talks
26mEvolution of Backstage: Declaring a New Route
34mPanel: Building a Healthy Backstage Plugins Ecosystem
11mBackstage Plugins Made Simple: No Rebuild Needed
05mThe Future is Backstage: Building a better platform from the...
29mWhat Does Backstage Really Offer – Looking Beyond Catalog and Templates and Into...
33mThe State of Backstage in 2025
05mThe Future is Backstage: Building a Better Platform from...
26mBackstage Plugin Development: Tales from the Trenches