La plus-value d'un portail développeur chez Back Market
summary
Back Market adopts Backstage to build a central DevPortal that cuts service creation from days or weeks to under an hour by orchestrating templates and workflows that call Terraform, GitHub/GitOps, a chassis code generator and custom TypeScript actions; a module crawler produces coupling scores stored in S3 and surfaced via two plugins (front/back) — plugins take 2–3 weeks to build — management starts acting on hot spots after scores expose trends; RBAC and naming inconsistencies force platform rework.
AI-written summary · about
chapters (12)
- 0:00Developer portal at Back Market
- 2:50Why Back Market needed it
- 4:57Scaling engineering problems
- 5:58Internal developer portal
- 8:04Central Hub benefits
- 11:39Service Bootstrap automation
- 16:32Coupling Scores for monolith
- 21:08Leadership buy-in challenges
- 22:33Platform tidying up
- 25:23Portal evolution lessons
- 27:10Portal reliability & adoption
- 35:02Q&A
related talks
28mThe Game-Changing Role of Developer Portals
38mEmbracing Developer Portals in Software Development
35mImproving Developer Experience with Backstage
25mThe Developer Portal: Open the Gate to Productivity 🚀
28mHow Did Backstage Make 500+ Developers Happy in a Highly Regulated Enterprise
47mImproving Developer Experience with Backstage
24mElevating Developer Efficiency with Developer Portal
06mFrom Portals to Productivity: The Next Leap for Backsta...