clean-architecture

You structure a .NET solution into four projects: Domain, Application, Infrastructure, and Api. This clean architecture layout enforces dependency rules, keeping domain logic independent from infrastructure and delivery layers.

The dependency rule in clean architecture requires inner layers like Domain and Application to remain independent of outer layers. Dependencies must always point inward toward the domain model, ensuring infrastructure and API layers do not pollute core business logic.

You wire HTTP endpoints to use cases by implementing a thin API layer that delegates requests directly to application use cases. This ensures the API layer remains free of business logic, acting only as a delivery mechanism for the .NET application.

Yes, clean architecture supports domain-driven design in .NET by placing entities and domain services in the core Domain layer. This guarantees domain-owned behavior remains isolated from infrastructure concerns like database access or external APIs.

Yes, dependency injection is essential for a four-layer .NET clean architecture. It enables dependency inversion by allowing the API layer to inject application services and infrastructure implementations without violating inward dependency rules.

You should avoid clean architecture for simple .NET applications where the overhead of four separate projects outweighs the benefit. If the domain model is minimal and infrastructure concerns are tightly coupled, this disciplined layout adds unnecessary complexity.