What We Learned During Our Journey in Using Backstage at DAZN
summary
DAZN implements Backstage starting March 2021 and launches it October 2021 to centralize a YAML manifest per repo ingested via a custom Manifest API and an identity API. It runs as a single container on AWS ECS Fargate behind an AWS Application Load Balancer with Azure AD via OpenID Connect, secrets bootstrapped from Vault, and RDS Postgres storage. The team automates catalog annotations, ships TechDocs, adds a contributed TV Target plugin, and now manages roughly 2,000 catalog entities across ~700 engineers.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:51Service directory need at DAZN
- 3:13Discovering Backstage
- 4:16Starting with plugins
- 5:18Backstage on AWS ECS
- 6:02Secrets and auth in Backstage
- 7:47External integrations
- 9:54Avoiding single source of truth
- 10:38Onboarding automation
- 12:04Maintaining Backstage
- 12:46Cultural impact on engineering
- 13:28Enabling contributions
- 14:51TV Target plugin
- 16:18Promoting Backstage
- 17:25Giving back to community
- 19:15Q&A
related talks
22mGetting Started with Backstage in 2023
39mUnlocking Backstage's potential: insights and solutions for a smoother developer experience
32mIs Backstage for me?
42mNavigating Backstage: A Year in Developer Life
27mIntroduction to Backstage
06mThe Future is Backstage
01h 01mClosing the documentation gap with Backstage.io
29mHow We Made Backstage Improve Developer Efficiency of 1000+ En...