Minimal Viable Architecture
summary
Argues that architecture must match a product phase: idea → starting → scaling → optimizing, so teams begin with a simple modular monolith on cloud PaaS, use open source and third‑party services for auth/payments, add instrumentation, continuous delivery and feature flags (LaunchDarkly/Optimizely/Split mentioned) to iterate fast. At scale, migrate via a pilot-and-incremental migration to polyglot microservices, prioritizing high‑value pages (eBay took 4–5 years and multiple rewrites). Claims massive microservice fleets are rare — most apps stay monolithic.
AI-written summary · about
chapters (9)
- 0:00Introduction to minimal architecture
- 3:35Evolution of big tech architectures
- 7:45Starting phase with monolith
- 13:03Building effective monoliths
- 21:22Signs to scale beyond monolith
- 23:30Scaling phase with microservices
- 27:00Migrating to microservices
- 31:57Optimizing mature systems
- 33:03Q&A on architecture scaling
related talks
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
50mTowards an Evolutionary Architecture
01h 25mCreating an Incremental Architecture for your System
01h 00mAgile Architecture
43mMonolith? Microservices? Who cares?
30mMoving Fast At Scale
47mMicroservices? Monoliths? An Annoying Discussion!
06mDo proper monoliths before you do microservices!