The Joy of Multiple Models
summary
Argues that the canonical “one big model” fails: the leasing example splits contract behavior into separate modules for sales and risk, each with its own data and domain model and an interface/event handoff between them. Uses Domain Storytelling to find activity boundaries, draws a context map, and implements models either as packages/modules or as independent services. Claims multiple small models reduce cognitive load and team coupling at the cost of deliberate duplication and sync work; recommends bounded contexts and cautious use of microservices.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:07About the speaker
- 3:15Domain story of auto leasing
- 6:46From domain story to domain model
- 10:23Problems with the one big model
- 13:32Why one big model fails
- 19:06What is a model?
- 21:55Multiple models in one domain
- 25:10Finding subdomains and bounded contexts
- 29:45Context maps and team organization
- 33:20Team structure and vertical cuts
- 36:52Implementing multiple models
- 38:14Strategic design vs microservices
- 40:03Further resources and call to action
- 41:09Q&A: Discovering subdomains
- 42:33Q&A: Handling communication steps
- 43:59Q&A: Duplication and synchronization
- 46:10Q&A: Loose coupling between domains
related talks
50mModel Mitosis: a dynamic pattern to deal with model tensions
46mModel Mitosis: Stop making the wrong choice between microservices and monolith
50mModel Mitosis: No More Confusing Microservices and the Monolith
48mModel Mitosis: Stop Confusing Microservices and the Monolith
50mAll Models Are Wrong: Lessons from Real DDD Projects
51mModel Mitosis: No More Confusing Microservices with Monoliths
43mModular Monoliths: The Architecture That Scales w Your Domain
49mRealizing Domain Design Through Architectural Modularity ...