Modular Monolith Instead of Microservices: How, When and Why
summary
The talk examines when to choose a modular monolith instead of microservices, arguing that a well-structured monolith can provide isolation comparable to microservices while keeping simpler debugging, deployment, and single-transaction workflows. It covers how to make a monolith modular, when to refactor a regular monolith into a modular one, and how to split modules out into separate services.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:19What is a monolith
- 7:10When to use monolith
- 17:25Why modular monolith
- 21:58Modular monolith example
- 39:04Modular monolith experience
- 51:53Summary versus microservices
- 55:48Q&A
related talks
01mModularization: Foundation of Microservices and Monoliths
45mOnce Upon a Time... Modular Monolith: The Quest for the Perfect Architecture
51mModularization: Foundation of Microservices and Monoliths
43mModular Monoliths: The Architecture That Scales w Your Domain
08mWhy we are writing a monolith, not a microservice
59mMajestic Modular Monoliths
01h 04mModular Monoliths and Other Facepalms
45mImplement a Monolith. But Make It Modular with Well-Enforced Boundaries