Minimum Viable Architecture
summary
Describes a concrete roadmap: start with rapid experiments (an Excel prototype or fake Google ads), use a single-app monolith for early teams, add logging, continuous delivery and feature flags, then pilot migration to services and pilot then reverse sort by revenue to maximize ROI. Gives painful specifics: an early eBay DLL hits 3.4 million lines and compiler limits, Amazon migrates 2001–2005 to per-service databases and launches AWS, and recommends seams, automated tests, per-service databases and ETL for analytics.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:10eBay architecture
- 4:54Amazon architecture
- 6:33Takeaways
- 8:33"Prototype" architecture
- 11:08"Just Enough" architecture
- 12:51Monolithic architecture
- 15:57Modular monolith
- 17:00Continuous delivery
- 18:00Feature flags
- 20:42When to rearchitect?
- 23:10Scalable architecture
- 26:17Microservices
- 29:06Incremental migration
- 34:46Carving up the monolith
- 36:34Extracting microservices
- 40:54Stable architecture
- 42:10Outro
- 42:21Q&A
related talks
26mArchitecting for scale
46mMaster Software Architecture: From Simplicity to Complexity
50mTowards an Evolutionary Architecture
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
44mPragmatic Microservices
36mDo Proper Monoliths before You Do Microservices!
51mScaling yout Architecture with Services and Events
23mOn the road from Monolith to Micro