Scale the Adoption and Delivery of Backend Plugins Using the New Bac...
summary
Shows how the Backstage new backend system lets teams migrate each search collator into its own backend module, register it via the addCollator extension point exposed by the search-index-registry, and remove the monolithic collator file and CODEOWNERS churn. Configuration like rebuild schedules lives in app config, the Backstage CLI repo-fix generates required package metadata, and the discovery feature loader can auto-detect modules from package.json so adopters add a package to enable a plugin with a single line change.
AI-written summary · about
chapters (8)
- 0:00Backstage’s new backend system
- 4:22New backend architecture
- 7:34Migrating collators to modules
- 11:48Simplifying setup with discovery
- 13:11Plugin and package metadata
- 16:45Improving discoverability
- 18:10Benefits of new backend
- 20:19Q&A on plugins
related talks
34mPanel: Building a Healthy Backstage Plugins Ecosystem
26mBackstage: Shaping the Future Of Developer Experience
35mImproving Developer Experience with Backstage
35mImproving Developer Experience with Open Source 1
32mAccelerating Collaborative Plugin Development
40mShaping The Future of Developer Productivity with Spotify Backstage
01h 01mBackdrop CMS: past and future
42mBeyond the Code: Evolving OpenSearch's Release Process for...