Model Mitosis: No More Confusing Microservices with Monoliths
summary
Explains how to decide between a monolithic application and microservices by focusing on the data and domain model. Covers causes of improper splits (model mitosis), consequences for coupling and maintainability, and practical guidelines to identify bounded contexts and when to keep a single deployable monolith versus split into services.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:00MVP user frustration
- 4:28Big Ball of Mud vs microservices
- 7:16Model tension
- 11:25Decoupling and duplication
- 13:10Domain Driven Design
- 15:18Domain separation
- 18:27Model specialization
- 21:15Anticorruption layer
- 27:16Dependencies and translation
- 31:07Tax calculation
- 37:07Production bug
- 39:12Schedule invariant
- 41:18Microservices and business needs
- 44:23Money pattern and context map
- 45:51Q&A
related talks
50mModel Mitosis: No More Confusing Microservices and the Monolith
48mModel Mitosis: Stop Confusing Microservices and the Monolith
46mModel Mitosis: Stop making the wrong choice between microservices and monolith
01h 01mModular Monolith Instead of Microservices: How, When and Why
39mConsidering Migrating a Monolith to Microservices?
01h 03mFrom Monolith to Microservices: Story and Practice
38mFrom Monolith to Microservices
42mQ&A - Monolith to Microservices
