EF Core natively supports Domain-Driven Design patterns without requiring custom wrappers. The post walks through configuring aggregates using EF Core's built-in configuration classes, achieving persistence ignorance by moving surrogate keys to shadow properties, implementing strongly-typed public IDs with value converters and alternate keys for cross-aggregate references, and applying CQRS where DbSets act as repositories, DbContext as unit of work, and LINQ to Entities as specifications. The conclusion is that wrapping EF Core to make it 'more DDD-like' is unnecessary since the implementation already exists.
โข12m watch time
Sort: