N-Tier Architecture in ASP.NET Core
Part 4: Build layered architecture for separation of concern, scalability and maintenance
From previous articles of the series it was demonstrated to setup REST API and architectural changes to separate concerns into repositories, controllers.
However for better modularity and separation of concern, separate layers can be configured for each process. Hence each layer is independent of each other and can be replaced by multiple implementations if needed. Layered design of REST API can be used to demonstrate usages of this architectural pattern.
Each of these layers should be Single Responsibility to avoid tight coupling and to support Separation of Concern. (Note that tiers and layers are used interchangeably but there is slight difference. Layer is known to be logical separation, where tier is actually physical separation. This is where some layers could be hosted in different physical locations due to independence of layers.)
Classical N-Tier Architecture
