
Clean Architecture organizes code so that business rules are independent of frameworks, UI, and infrastructure.
Key rules:
1. Dependency rule — source code dependencies point inward, toward the domain.
2. Use cases — application layer orchestrates domain behavior.
3. Interfaces at boundaries — infrastructure implements interfaces defined in inner layers.
Typical layers:
Domain → Application → Infrastructure → Presentation (API/UI)
Architecture impact: Clean Architecture makes your .NET Core app testable, maintainable, and resilient to framework changes.
Reference:
TaskLoco™ — The Sticky Note GOAT