Getting to DDD: Pragmatic or Principled?
summary
Argues that adopting parts of DDD incrementally wins where strict purity loses, using concrete steps: audit a legacy 700-table database, map domains into smaller bounded contexts, refactor code to introduce an aggregate root, and let Entity Framework persist without forcing a separate data model. Recommends practical tactics that work—event storming, pair/mob programming, extracting value objects, one‑way navigations—and reports these stop team resistance and deliver measurable architecture simplification on real projects.
AI-written summary · about
chapters (14)
- 0:00Introduction to the topic
- 3:59The problem with dogmatism
- 8:45The mirror exercise
- 15:21Overcoming learning barriers
- 17:21Practical implementation
- 18:10Structure before language
- 20:58The garden and code analogies
- 26:58The importance of boundaries
- 32:19Personal journey into DDD
- 35:24Applying DDD to ORMs
- 45:27Managing technical friction
- 50:11Consulting with teams
- 53:53Strategic and tactical design
- 57:24Getting started strategies
related talks
38mIntroDDDuction
01h 11mAn introduction to DDD
01h 03mExposing the not-so-secret practices of the cult of DDD
01h 03mExposing the not-so-secret practices of the cult of DDD
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
58mDDD really matters!
01h 03mExposing the not-so-secret practices of the cult of DDD
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book