About service-oriented components and modularization

 

 

 

 

 

 

 

The bottom layer is the infrastructure and database services. In the databases used by various underlying services, databases can be independent and distributed. Too much data interaction and transmission should not be established between databases. The specific data synchronization and interaction must also be registered on the ESB service bus to provide data services according to certain standards.

There are two types of services and engines on the ESB Enterprise Service Bus. One is the engine that provides the basic technical architecture and service, and the other is the engine that provides the service SOA service. Permission modeling, process modeling, organizational structure modeling, reports, charts, and data services highlighted in quick software development can all be abstracted as standard technical service engines. These engines allow us to quickly build a business software development platform. Another type is business-related engines, such as procurement service engines, inventory service engines, sales services, and credit service engines. These engines abstract general rules of common businesses, at the same time, you need to consider the configuration and scalability in different scenarios.

When standard SOA services have been exposed, we can see that we can orchestrate various business SOA services through Business Process Orchestration to complete a complete business operation and process. A complete business flow is the orchestration and combination of various SOA services and engines. In the process of Process Orchestration, we can also set various business rules and create branches. Therefore, an independent business rule engine can be abstracted here.

To implement the service concept of SOA, the service-oriented architecture model SCA is required. SCA is a complete set of development and deployment specifications based on the SOA idea. In the past, when implementing SOA, we usually expose services through web services, that is, only componentized and reusable services are implemented at the data layer and service. Here our opinion is that with the development of SCA, a complete business service should be vertically split, that is, a complete set of reuse is provided from the UI-> service-> data. As for the front-end, it is a highly independent UI part that complies with certain standards and specifications. Such panels can be flexibly configured and assembled in the portal. If our services do not reach the UI Layer, we still cannot solve the problem of repeated development.