Details SCA V1.0 specification (3)-domain and business

It has been nearly six months since I wrote the first article "details SCA V1.0 specification (1) -- component and implementation. At such a long interval, the content originally conceived cannot be written in a coherent manner. Stable income and ample time are a contradiction. How many people are constantly looking for a balance between them.

When writing a blog, I am sorry that I cannot write all the content that I think. In fact, SCA can be viewed in many different fields. From the perspective of Data Structure, SCA can be viewed from the perspective of software development models, and SCA can be viewed from the software life cycle. The adaptability and practicability of SCA can be seen from different angles. Let's talk about domain and business.

First, what is domain? Isn't domain a domain! What does the domain mean? Internet connection involves the concept of a domain name and a LAN in a unit. This domain is actually the scope of its function and has a division boundary. A domain is a range, a region, and the content contained in this region has a common feature. In the same domain, different domains have obvious boundaries and different features.

Each domain in SCA is divided for a service function. Each domain corresponds to a certain business scope. This business domain may be a sub-system or a module. For example, the finance department may have a financial system that corresponds to the domain of a financial system. Human resources correspond to the talent management domain. Each domain provides functions for the business in the domain. Each domain is identified by a URI.

The model is built from the domain in SCA. The uri id and domain model of a domain can be one-to-one or one-to-many. A URI must correspond to only one domain. There is no domain concept in the v0.9 specification, and SCA can still run, so domain is a logical layer.

Domain domain, I understand as two layers. The first layer is the naming layer, which establishes an association between the URI and the domain, and uses the URI to access the domain model. The second layer is a composite layer, objects in the model are organized in the form of composite components, but these components are composed of objects in memory, rather than generated through external file parsing. These objects in the memory are initialized, constructed, parsed, and managed through the SCA container.

<To be continued>