clean-architecture

Structure your .NET application using a 4-project layout: Domain, Application, Infrastructure, and Api. This clean architecture separates domain rules from infrastructure and delivery concerns, enforcing dependency inversion so the Domain layer stays framework-agnostic and stable.

Keep EF Core persistence implementations behind Application and Domain abstractions. This clean architecture pattern treats infrastructure as a plugin, keeping external services and persistence implementations isolated so you can swap providers safely without affecting business rules.

Implement use cases as focused Application handlers that coordinate domain objects and persistence. This clean architecture approach treats commands and queries as single handlers, acting as a unit of work to map HTTP requests to use cases without embedding business logic in the API layer.

Yes, this clean architecture supports minimal-api style endpoint wiring. The thin API layer maps HTTP to use cases and returns responses directly, relying on Application handlers to coordinate domain behavior and persistence without embedding business logic in the endpoints.

Your domain layer likely lacks strict dependency inversion. Clean architecture enforces inward dependencies so the Domain layer stays framework-agnostic; infrastructure implementations must sit behind abstractions defined in the Application or Domain layers to prevent this coupling.

Using a mediator pattern aligns with this clean architecture approach by routing commands and queries to focused use case handlers. This keeps the Application layer organized and ensures infrastructure implementations remain hidden behind Application and Domain abstractions.