DDD in Microservices: Complexity versus Complexity
summary
A case study from a large bank about adopting Domain-Driven Design (DDD) together with a migration to microservices. It describes using DDD techniques—bounded contexts, speaking the ubiquitous language with stakeholders, and reorganizing the codebase—to manage complex business logic, improve code quality, and lessons learned from applying both approaches in tandem.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 6:36Reasons for DDD
- 8:20DDD strategic design
- 13:22Context mapping mistakes
- 16:55Aggregates in microservices
- 19:44Service relationships
- 21:55Ubiquitous language and bounded contexts
- 22:16Layered architecture in services
- 25:14Skeleton pattern issues
- 28:28Code specifics and domain events
- 33:04Data validation in DDD
- 35:53Read challenges in microservices
- 38:20Business logic separation
- 44:01DDD for technical services
- 46:09Implementation results
- 51:22Q&A
related talks
40mMicroservices without DDD is risky business!
49mDDD & Microservices: At Last, Some Boundaries!
56mMicroservices and Domain-Driven Design — The Strategic Parts
01h 00mFrom Domain Driven Design DDD to Delivery
44mStrategic Domain-Driven Design for dummies
39mLessons Learned from 10+ Years with Domain Driven Design
45mUsing DDD To Decompose Your Monolith
47mDomain-Driven Design: A Complete Example