Domain-Driven Design: back to the roots
summary
Explains that Domain-Driven Design is essentially object-oriented principles applied at scale, demonstrated on a banking example: identify entities by ID, make addresses immutable value objects, and group consistency into aggregates while iterating the model using eventstorming. Recommends small aggregates for easier evolution, mapping teams to bounded contexts with identity reconciliation, and integration patterns including open host/published language, ACL/anticorruption layer, and domain events via pub/sub, citing Evans’ 2003 patterns and advocating pragmatic iteration rather than perfect first models.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:10First day at BXL bank
- 15:59Context boundaries in DDD
- 24:05Teams and context coupling
- 31:09Entities and value objects
- 44:22Modeling and encapsulation
- 52:09Subdomains and solution space
- 55:15Q&A
related talks
59mDomain-Driven Design - Where Rubber Meets the Road
46mDomain Driven Design The Basics
38mWhat I talk about when I talk about Domain Driven design
48mDomain-Driven Design tactically and practically
47mDomain-Driven Design: A Complete Example
41mDomain-Driven Design: Hidden Lessons from the Big Blue Book
45mDon't Overdose on Domain-Driven Design
56mMicroservices and Domain-Driven Design — The Strategic Parts