Your DDD Abstractions Are a Waste of Code

A pragmatic critique of over-engineered DDD abstractions around Entity Framework Core. Instead of building heavyweight wrapper classes for repository, unit of work, and specification patterns, the author advocates using thin interfaces that delegate directly to DbContext — treating DbSet as the repository, LINQ to Entities as the specification, and DbContext itself as the unit of work. The result is persistence-ignorant, testable application code with minimal boilerplate. For queries, named query classes in the infrastructure layer replace abstract specification hierarchies. The approach keeps DDD's intent (decoupling, clarity) while eliminating unnecessary layers.