Chopping the monolith
summary
Argues that microservices rarely fix org problems and are worth it only when many people work on one codebase—rough guideline: around 70 developers. Demonstrates a pragmatic alternative: isolate the fast‑changing pricing logic from an e‑commerce monolith, run a demo with Docker Compose and an api6 API gateway backed by etcd, copy a Kotlin price function into a tiny service (converted to JavaScript), reconfigure routing at runtime and serve pricing from the new endpoint without redeploying the monolith.
AI-written summary · about
chapters (13)
- 0:00Introduction and disclaimer
- 2:14Microservices myths and reality
- 6:27Organization and Conway’s law
- 10:07Why microservices fail in practice
- 11:30Evaluating microservices benefits
- 17:10Monolith limitations and quick changes
- 21:57Strangling the monolith concept
- 24:12Demo introduction and setup
- 27:30Demo: Initial monolith flow
- 28:31Demo: Adding pricing route
- 30:39Demo: Isolating pricing logic
- 32:53Resources and closing
- 33:36Q&A session
