How Architecture Decision Records Shaped Spotify's Engineering Culture

Episode notes

In 2018, Spotify's playlist team faced mounting coordination costs across three backend services. Instead of a costly rewrite, they wrote an Architecture Decision Record (ADR) that sparked a cultural shift. This episode traces the impact of ADR #42 - the decision to adopt event-driven architecture for playlist updates - which reduced latency by 40% and cut cross-team meetings in half. We explore how Spotify turned decision-making into a scalable artifact, the templating process they used, and why ADRs have become a cornerstone of their engineering org. Lucas and Luna discuss the tension between written records and agility, and how one document can cascade into organizational change. For CTOs and senior engineers wrestling with technical debt and alignment, this is a blueprint for making decisions that stick without grinding the team to a halt.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

• Durable Execution for Real‑World Failures with Temporal’s Cornelia DavisPlatform Engineering Podcast · on Event-driven architecture96 / 100
• Embedding Value in the Insurance MarketTech means Business · on Event-driven architecture63 / 100
• EP1017: The Quiet Reinvention of Transaction BankingIBS Intelligence Global FinTech Interviews · on Event-driven architecture44 / 100
• Why Your API Should Use Webhooks for Event DeliveryThe Developer Tools Podcast with Fexingo · on Event-driven architecture

• How Airbnb Rebuilt Its Search for 100 Million Listings72 / 100
• How GitHub Migrated 100 Million Repositories to a New Storage Engine76 / 100
• How Dropbox Rebuilt Its Sync Engine for 700 Million Users85 / 100
• How Skyscanner Migrated 300 Microservices to Event-Driven Architecture85 / 100
• How Palantir Rebuilt Its Foundry Ontology for Government AI Deployments85 / 100