Mapping Well-Designed Domain Models with EF Core 2.1
summary
Claims that EF Core 2.1 actually maps well‑designed DDD models: it supports encapsulated collections via private backing fields, maps value objects with owned types, offers value converters for custom CLR types and shadow properties for auditing, and improves one‑to‑one and backing‑field scenarios. Workflow includes build plus dotnet ef dbcontext info and integration tests. Many‑to‑many still requires an explicit join entity; owned collections and other tweaks land in later releases; repository demos and GitHub branches validate the examples.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:01Mapping with EF Core (2.2*)
- 3:43FOCUS ON DOMAIN not secondary or cross-cutting concerns
- 30:51Encapsulate Collections
- 43:20SHADOW V PROPERTIES Great for storing audit data
related talks
59mMapping DDD Domain Models with EF Core 2.1
50mEntity Framework Core 2.2 and beyond: what's cooking?
56mPractical Domain-Driven Design with EF Core
44m10 things you didn't know EF Core can do
46mEntity Framework Core 2.1 – what’s new?
59m10 things you didn't know EF Core can do
55mPractical Domain-Driven Design with EF Core
47mEF Core 6: Working on the Bucket List