Why we are writing a monolith, not a microservice
summary
A decade old monolith splits into app catalog and a new pricing module rather than two over‑the‑network services after usage analysis shows they'd be chatty services. The team builds a modular monolith with domain modules, explicit interfaces, and no HTTP chatter; reasons given are improved reliability and developer productivity, and the design supports later extraction to a microservice if independent scaling becomes necessary — it is working great so far.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:25Microservice
- 2:10Abstraction
- 2:36Boundaries
- 4:05Conway's Law
- 5:53Modular Monolith
- 6:52Shape code structure
related talks
01h 01mModular Monolith Instead of Microservices: How, When and Why
42mChopping the monolith
23mMicroservices within a Monolith
36mDo Proper Monoliths before You Do Microservices!
47mMicroservices? Monoliths? An Annoying Discussion!
57mModularizing the Monolith
31mChopping the monolith
59mMajestic Modular Monoliths