Domain-Driven Design tactically and practically
summary
Covers tactical Domain-Driven Design implemented in .NET (C#) to build a clean, adaptable domain model for complex business rules. Explains concrete practices: naming, encapsulation, infrastructure independence, Law of Demeter, composition over inheritance, low coupling/high cohesion, aggregate boundaries, persistence and validation, using rich domain types instead of primitives, and supporting architecture plus unit testing to enable change.
AI-written summary · about
chapters (12)
- 0:00DDD introduction
- 2:59Clean code and domain model
- 5:09OOP basics
- 8:22Commands, aggregates and events
- 15:17Ubiquitous language and object behavior
- 22:50Infrastructure ignorance and architecture
- 27:49Business rule validation
- 33:13Eventual consistency and aggregates
- 35:23Business class design
- 40:05Unit tests in DDD
- 43:02Recommended books and summary
- 45:38Q&A
related talks
59mDomain-Driven Design - Where Rubber Meets the Road
38mWhat I talk about when I talk about Domain Driven design
58mImplementing Domain Driven Design as a Pragmatic .NET Developer
55mDomain-Driven Design: back to the roots
46mDomain Driven Design The Basics
41mDomain-Driven Design: Hidden Lessons from the Big Blue Book
49mHow to cook Domain Driven Design
42mDomain Driven Design - So Your Code Speaks Plain Language