. NET application architecture design-query-Oriented Domain-driven design practices (adjust the traditional three-tier architecture, and add maintenance-oriented business switches)

Reading directory:

1. background 2. add the core domain model to the business layer (introduce the DomainModel to make the logic and data fall into a complete business object. unified coordination Layer Application Layer (added to the coordination Layer to convert the DomianModel) 4. convert from a flat data structure to an OO architecture (using a rich OO code structure) 5. content in DomainModel (Specification with switch and Specification with SOA) 6. application of pattern, reconstruction, and unit test in domain model 1. background

Due to the time-related nonsense, go straight to the topic. If you are not familiar with the domain-driven design, familiarize yourself with the related topics or refer to the following two articles:

. NET domain-driven design-first taste (questions, patterns, principles, tools, processes, frameworks, and practices). This article analyzes the basic spirit of domain-driven design in detail;

. NET domain-driven design-Practice (going bright through the fog). This article describes a basic practice of domain-driven design and records the practical process and modeling techniques;

DomainModel is composed of many fine-grained objects. According to previous lessons (dismounting Object behavior and data to get a defective Object), we now bind logical behavior and data together, A rich domain model is formed, which is also one of the object-oriented design principles.