Iii. Cloud-oriented. net core development framework project solution,. netcore
Based on the concept of domain-driven design, the solution for building a development framework is as follows:
* The solution is being transformed and will be gradually improved along with the transformation process.
Solution directory |
Corresponding Domain Design Layer |
Description |
Infrastructure |
Infrastructure Layer |
Underlying class library developed |
Core |
|
Including core components such as cache, configuration, logs, common tools, and data access |
Core. Caching. Redis |
|
Implementation of Redis distributed cache |
Core. Data. Entity |
|
EntityFramework encapsulation class library |
PlugIns |
|
It is mainly used to encapsulate sdks for external products. |
Domain |
Business Domain Layer |
Business Domain Model and business logic |
Model |
|
Business Entity |
Model. Mapping |
|
Database ing of business entities |
Repoistory |
|
Business warehousing implementation |
Repoistory. Interface |
|
Business warehousing Interface |
Service |
|
Business Logic implementation |
Service. Interface |
|
Business logic interface |
AppService |
Application Service Layer |
SOA to provide services to the upper layer |
AppService |
|
External Application Layer services |
AppService. Interface |
|
External Application Layer Service Interface |
Presentation |
User Interface presentation layer |
Components and controls for Windows/Web Applications |
Web. Library |
|
Web site class libraries and controls |
Web. Controls |
|
Web controls |
Client |
Client |
Client implementation |
Areas |
|
Areas of the Client |
Common |
|
Public Region |
DataWare |
|
Data warehouse area |
SampleWebApp |
|
Sample website |
StaticWebApp |
|
Static resource website |
ConsoleApp |
|
Console applications are mainly called by background tasks. Similar to the original Windows Service |
|
|
|
Focus on the Areas section: We divide the entire client application according to the business module, which can be divided into common Areas, portal Areas, data warehouse Areas, workflow and form Areas, and CMS Areas. To write less words, I listed only the portal and data warehouse areas in the table. In this way, when each client application is created, you only need to reference the relevant regions, not necessarily all regions are referenced. This is the so-called plug-in method. Next, we will take a closer look at ApplicationPart practices and see if we can change the Area to ApplicationPart.