Lessons Learned from 10+ Years with Domain Driven Design
summary
Ten-plus years of trial and error with Domain Driven Design: tactical DDD applied to messy migrations fixes data integrity but creates oversized aggregates; a second project using a hybrid document/graph DB exposes DDD mismatch and poor query performance; then strategic DDD with bounded contexts, hexagonal architecture, Spring Boot and Spring Data JPA yields a successful suite of independently deployable services after a 3.5 year project; practical techniques include event storming and domain primitives for validation.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 3:56First contact with DDD and early struggles
- 7:09Tactical DDD and initial project attempts
- 9:18Second project failure and imposter syndrome
- 12:11Discovering strategic DDD and bounded contexts
- 14:44Hexagonal architecture and domain events
- 18:37Event storming and its benefits
- 22:29Third project success with strategic DDD
- 25:26Secure by Design book and domain primitives
- 28:58Critique of current best practices
- 34:34Key takeaways and closing remarks
related talks
59mDomain-Driven Design - Where Rubber Meets the Road
29m20 Years of Domain-Driven Design: What I’ve Learned About DDD
38mWhat I talk about when I talk about Domain Driven design
44mStrategic Domain-Driven Design for dummies
48mDomain Driven Design: The Good Parts
01h 00mFrom Domain Driven Design DDD to Delivery
58mImplementing Domain Driven Design as a Pragmatic .NET Developer
01h 01mThe DDD Do-Over: Domain-Driven Design Lessons Learned