#domain-driven-design

Articles tagged with #domain-driven-design

Vogen vs StronglyTypedId in .NET: Which Should Your Team Use in 2026?
Primitive obsession is one of the subtler bugs in .NET APIs - int orderId, int customerId, int productId all look identical to the compiler, and nothing stops you from passing them in the wrong order.
Jun 21, 202610 min read5
Domain Events vs Integration Events in .NET: Which Should Your Team Use?
Most .NET teams reach for "events" as a general-purpose solution long before they have a clear model for what kind of event they're working with. The confusion is understandable - both domain events a
May 30, 202611 min read
EF Core Owned Entities vs Complex Types for Value Objects
When you adopt Domain-Driven Design in a .NET codebase, one of the first decisions your team faces is how to map value objects to the database. For years, OwnsOne and OwnsMany were the only first-clas
May 23, 202611 min read72
The Anti-Corruption Layer Pattern in ASP.NET Core: When to Use It and How
Every enterprise codebase eventually develops a problem that no design pattern can fully prevent: the gradual spread of someone else's model into your own. It might be a legacy ERP system whose data s
May 15, 202614 min read3
The Specification Pattern in ASP.NET Core: When to Use It and How
Enterprise .NET teams integrating the Specification Pattern into their ASP.NET Core applications consistently face the same fork in the road: does this pattern genuinely solve a data-access problem, o
May 7, 202613 min read8

#domain-driven-design - Coding Droplets