Clean Architecture in ASP.NET Core: What Actually Belongs in Each Layer

Clean Architecture gets misapplied constantly - usually by putting Entity Framework attributes in Domain entities, or business logic in controllers. The rule of thumb: Domain has zero framework dependencies, Application defines interfaces the outside world implements, Infrastructure is the only layer that knows about EF Core or Identity, and Web only orchestrates HTTP concerns.

Get this boundary right early - untangling it later is expensive.