Spotify's open platform for shipping at scale (Interview)

We’re joined by Jim Haughwout (Head of Infrastructure and Operations) and Stefan Ålund (Principal Product Manager) from Spotify to talk about how they manage hundreds of teams producing code and shipping at scale. Thanks to their recently open sourced open platform for building developer portals called Backstage, Spotify is able to keep engineering squads connected and shipping high-quality code quickly — without compromising autonomy.

Join the discussion

Changelog++ members save 4 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• Linode – Our cloud of choice and the home of Changelog.com. Get started on Linode today with a $100 in free credit. You can find all the details at linode.com/changelog
• Pixie – Pixie gives you a magical API to get instant debug data. The best part is this doesn’t involve changing code, there are no manual UIs, and this all lives inside Kubernetes. Pixie lives inside of your platform, harvests all the data that you need, and exposes a bunch of interfaces that you can ping to get the data you need. It’s a programmable edge intelligence platform which captures metrics, traces, logs and events, without any code changes.
• Retool – Retool makes it super simple to build back-office apps in hours, not days. The tool is is built by engineers, explicitly for engineers. Learn more and try it for free at retool.com/changelog
• Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com.

Featuring:

• Jim Haughwout – GitHub, LinkedIn, X
• Stefan Ålund – GitHub, LinkedIn, X
• Adam Stacoviak – Website, GitHub, LinkedIn, Mastodon, X
• Jerod Santo – GitHub, LinkedIn, Mastodon, X

Show Notes:

• spotify/backstage
• What the Heck is Backstage Anyway?
• Backstage has been accepted into the CNCF Sandbox
• Backstage on CNCF landscape
• MkDocs - Project documentation with Markdown
• Gary Niemen on how Spotify is solving internal technical documentation

Something missing or broken? PRs welcome!