NET common project architecture patterns, how many do you know? (with a usage poll)

preamble

Project architecture patterns play a vital role in software development; they provide developers with a set of guiding principles for organizing and managing code to improve the maintainability, scalability, reusability, and testability of software.

If you have any other project architecture patterns to recommend, feel free to leave a comment at the end of the article 🤞!!!!

Project Architecture Patterns Usage Collection (WeChat Voting, please open in WeChat to participate):/s/kr1vlt4tj3dSyXyRv-GqOw

three layer architecture (OSI)

 

Three-tier architecture is a classic software architecture pattern that divides an application into three main layers: the representation layer (UI), the business logic layer (BLL), and the data access layer (DAL).

Hierarchical responsibilities

• Representation layer (UI): responsible for the user interface and user interaction, is the part of the user direct contact.
• Business Logic Layer (BLL): handles business rules and business logic and is the core part of the application. It is responsible for data processing, validation, calculation and other business operations.
• Data Access Layer (DAL): responsible for interaction with the database, including CRUD (create, read, update, delete) operations on data.

MVC architecture

The MVC architecture pattern distinguishes an application into three main components: the model, the view, and the controller. This pattern facilitates the separation of concerns, as user requests are routed to the controller, which is responsible for collaborating with the model to perform user actions and/or return request results. This greatly improves the maintainability and scalability of the application.

Hierarchical responsibilities

• Model: represents the state of the application and any business logic or operations that should be performed by it. The business logic should be encapsulated in the model along with any implementation logic that maintains the state of the application.
• Views: are responsible for displaying content through the user interface. They use the Razor view engine to embed .NET code in HTML markup. There should be minimal logic in the view, and any logic in it must be relevant to the content being displayed.
• Controller: The component that handles user interaction, uses the model, and ultimately selects the view to be rendered. In an MVC application, the view only displays information; the controller handles and responds to user input and interaction. In the MVC model, the controller is the initial entry point and is responsible for selecting the type of model to use and the view to render.

DDD Layered Architecture

Domain-Driven Design (DDD) is a software design methodology and philosophy, proposed by Eric Evans in 2004. It transforms complex business logic into maintainable and extensible software systems through an in-depth understanding of the business domain.The core of DDD lies in the creation of a rich domain model that reflects business entities, business rules, and business processes.

DDD emphasizes the domain model as the core to drive software design and development.

Hierarchical responsibilities

• Representation Layer (UI): Responsible for handling the user interface and user interaction, which can be in the form of a web interface, a mobile application or a desktop application, etc. The representation layer is responsible for receiving user input and presenting data to the user, but it contains no business logic. The UI is responsible for receiving user input and presenting data to the user, but it does not contain business logic.
• Application: The intermediary between the representation layer and the domain layer, orchestrating business objects to perform application-specific tasks and implementing use cases using application logic.
• Domain: Contains business objects and business rules, and is the core of the application. The design of the domain layer should follow the principle of domain-driven design, and encapsulate the business knowledge and business logic in the domain model through in-depth understanding of the business domain, in order to improve the maintainability and scalability of the software system.
• Infrastructure: Provides technical infrastructure support, such as database access, message queuing, caching, and so on.

clean structure

Clean Architecture (Clean Architecture) is a software architecture design principles, by Robert C. Martin (Robert C. Martin), it aims to make software systems more flexible, maintainable and testable, and its core goal is to build a simple, flexible and easy to maintain the system structure.