-
Book Overview & Buying
-
Table Of Contents
Clean Architecture with .NET
By :
When adding new functionality in a Clean Architecture application, the starting point is usually the Application layer. This is where use cases are expressed, orchestrating the flow between domain rules and external concerns. Beginning here helps ensure that new features are driven by business needs rather than technical details, keeping the architecture aligned with its core principles.
That said, you'll often need to create or refine supporting elements in the Domain layer first — for example, defining a new entity or adding a method to enforce a business rule. In practice, the Application layer sets the direction, while the Domain layer supplies the building blocks. Together, they establish a clear boundary that keeps the business logic insulated from infrastructure and presentation concerns.
This inside-out mindset is key. Rather than seeing your application as "just a web app" or "just an API," you treat those as entry points...