Enterprise Application Architecture Model (3)

Chapter 3 ing to relational databases

First, you need to separate the SQL statements from the domain logic and put them in an independent class. These classes create an entry for the database table.
The entry includes the row data entry and table data entry (through the dataset ). As the domain model increases, data ing (O/R Mapping) should be used ).
During data ing, there is also a relationship ing, that is, the problem between the relationship between the database table and the class (object) structure, and how the hierarchy of inheritance and combination can be expressed in the data table.
Database Connection is another concern.

Object-link ing is a must-have problem and requires deep learning.

Chapter 7 Distribution Strategy

First Law of Distributed Object Design: Do not use distributed objects. In this case, the cluster system is used.

Web Service is usedProgramInteraction between systems (used for integration between systems), rather than communication between layers in the program!

Chapter 8

Technologies that need to be carefully considered for development: continuous integration, test-driven development, and reconstruction.

When talking about field modification in the database table, there should be a lot of modifications to the use of different domain logic strategies in the form of transaction scripts, while for the use of Domain Models, through better design decomposition, many businesses can be separated, so that the coupling degree of each part is the lowest, and the part that needs to be modified will be reduced. For projects, we can achieve good development efficiency through "continuous integration, test-driven development, and reconstruction.