Practical Domain-Driven Design with EF Core
summary
A small florist subscription app is refactored from an anemic model into a behavior-rich domain using .NET Core, EF Core and Mediator: constructors validate and set active status, private parameterless ctor supports EF, collections become read-only, and discount rules (>$100 → 20%, >$1000 → 50%) move into a domain service with double dispatch; domain events are queued and dispatched via EF Core SaveChanges interceptor and Mediator publish, value objects map with owned entity mapping, and unit tests run green after each change.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:26What is Domain-Driven Design?
- 1:44What is Domain Model?
- 5:44Sample Domain
- 22:42Extract Methods
- 23:22Encapsulate Collection
- 31:25Double Dispatch
- 32:44Domain Events
- 47:38From Primitive Obsession to Value Objects
- 48:25Where is the Repository?
- 49:30Can the Unit of Work help us?
- 50:08Embrace the DbContext
- 51:55Base Entity ID
related talks
56mPractical Domain-Driven Design with EF Core
59mMapping DDD Domain Models with EF Core 2.1
46mMapping Well-Designed Domain Models with EF Core 2.1
01h 10mModern Data Applications with Entity Framework 7
45mGetting Started with Cosmos DB + EF Core
01h 01m10 things you didn't know EF Core can do
44m10 things you didn't know EF Core can do
01h 00mGetting the best out of Entity Framework Core