Microservices? Monoliths? An Annoying Discussion!
summary
Monolith in practice had hour-plus compiles, ~50 minute startup and weekend two‑day releases; another project ran quarterly releases with ten weeks of testing and wanted to deploy several times per day. Microservices win when teams need independent scaling or independent deploys, and they enable information hiding at the team/bounded context level. Netflix runs thousands of services but still ships features and $25B revenue shows it can work. Key failures come from bad modularization, org rules that force all services to deploy together, or missing verifiable goals like an app‑store 4.5+ rating.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:04My First Large Project
- 5:00Another Project
- 9:28Typical Monolith Architecture
- 10:56We have 1.000 microservices!
- 15:49Why Netflix Works?
- 21:00Microservices: Technical Benefit
- 24:00Microservices: Productivity
- 25:00is enabling teams
- 26:48Microservices enable independent deployment & technology decisions
- 30:12The Essence of Architecture
- 32:40Verification • For performance
- 33:38My Experience
related talks
19mMicroservices vs. Monolith for Scalability and Efficiency
13mYou're not Netflix (Microservices, Monolith architecture)
57mEmbracing Microservices
01h 00mMicroservices, Where Did It All Go Wrong?
26mMicroservices
48mMicroservices vs The Distributed Monolith
38mMonolith vs. Microservices
55mMicroservices, Where Did It All Go Wrong