Architecture Evolution Stories: Airbnb, Netflix & Shopify
Three companies hit the same growth wall and gave three different answers: layered SOA, cloud microservices behind a gateway, and a deliberately modular monolith split into pods. Each story is told stage by stage (trigger, constraint, decision, cost, lesson) from primary sources, then turned into a staged plan for a NestJS monolith
About 130 minutes · 17 exam questions · 11 interview questions · 2 code labs
What you will learn
- Why evolution stories win interviews, and the five-beat way to tell one
- Airbnb, stage 1–2: from the Monorail to a four-tier SOA
- Airbnb, stage 3: how they actually moved traffic (dual reads, shadow writes, ramps)
- Airbnb, stage 4: what broke after SOA, and what they say about it now
- Netflix, stage 0–1: a 3-day outage, a 7-year cloud rebuild, and why chaos engineering was born there
- Netflix, stage 2–4: NCCP, the orchestrator that became a monolith again, and the Zuul gateway
- Netflix, stage 5–6: from one team's graph to GraphQL federation, and the safe mobile migration
- Shopify, stage 1–2: the deliberately modular monolith and Packwerk
- Shopify, stage 3: pods for tenant isolation, and the few things that left the monolith
- Three answers to the same growth pressure: SOA vs microservices vs modular monolith
- Anti-patterns seen in these migrations, and the fitness function that catches each
- Applying it: a staged plan for a NestJS monolith at an Indian startup
Previous: Real-World Dissections: Famous Architectures & Outages, Explained