Abolishing "Shaft" and turning to "Soa", why should we adopt SOA?

  Currently, the architecture of mainstream software projects is similar to "Silo", where databases, intermediate layers, and client performance layers are available. The databases of each application system belong to different silos. When our informatization develops to a certain extent and the systems that have been developed and run online need to be integrated or implement data sharing, we have to "wear holes" in the shaft to access the database through different "shafts. When objects in a database change, the impact on other systems becomes "unknown" and "uncontrollable.

When we want to call system services, we also need to break through the shaft. If the enterprise's IT resources, such as: client programs, intermediate layer business processing, support platform, data processing, raw data and standard data sources, the resources of each application system are integrated by means of the Message Mechanism Based on layers, and the resources are organized according to the different functions and functions of each layer.

 We are now using new design ideas,SOAIt is a service-oriented architecture, more specifically a kind of architecture style;SOAIs a style and concept, emphasizing the combination of resource sharing and reuse, Enterprise Architecture dynamics and flexibility;SOAThrough modular and open standard interface design, enterprises can achieve close integration of IT and business, and improve the flexibility of business processes.

 

    Different functional modules in the SOA system can be divided into seven layers: the first layer is the existing program resources of the system, such as ERP or CRM systems. Layer 3 is the component layer. In this layer, we use different components to encapsulate the functions of the underlying system. Layer 2 is the most important service layer in the SOA system. In this layer, we need to use underlying functional components to build services with different functions that we need. In general, services in SOA can be mapped to any functional module in a specific system, but they can be roughly divided into the following three types in terms of functionality: (1) Business Service) or a business process ). This type of service is a service that an enterprise can expose to external users or partners. For example, submit a loan application, user credit check, and loan credit query. (2) commercial function services, which perform specific commercial operations and are also called by upper-level commercial services, however, in most cases, such services are not exposed to external users for direct calls, such as searching user account information and storing user information. (3) Technical Function Service (Technical Function Service), which mainly implements some underlying technical functions, such as Log Service and Security Service. The 4th layer above the service layer is the Business Process Layer. In this layer, we use encapsulated services to build business processes in the business system. On the business process layer, the presentation layer is the 5th layer. We use the presentation layer to provide user interface services. This layer can be built using a portal-based system. The above five layers all need an integrated environment to support their operation. The Enterprise Service Bus (ESB) in layer 6th provides this function. Layer 3 provides some auxiliary functions for the entire SOA system, such as service quality management and security management.