SOA-based banking system architecture

Part-1 "Brief Introduction"

1. through the introduction of Service Oriented Architecture (SOA), Enterprise Service Bus (ESB), adapter (Adapter) and component-oriented technology, try to build a unified business process Service platform to realize process-oriented service integration.

2. The focus of traditional banking informatization is basically the construction and transformation of a single business system, with many internal systems and no use of mutual resources.

3. based on the SOA (Service Oriented Architecture) system architecture, the bank can realize the seamless integration of the business systems at the lowest cost, on the basis of making full use of the existing system resources.

4. SOA (service-oriented architecture)-based system architecture, through the encapsulation of business systems as a service, with an enterprise service bus (ESB), to achieve a variety of production, management and decision-making and other important information systems between the efficient integration.

Part-2 "Service Oriented Architecture (SOA ) "

1. Service-Oriented Architecture (SOA) is an architectural model that advocates architectural design principles such as component, loose coupling, isolation concerns, and standardization.

2. real-world applications can encapsulate their business functions, information or processes as basic components-standardized services (e.g., account opening, payment, interest-bearing services, etc.), which serve other applications through a loosely coupled SOA architecture.

3.The SOA includes service providers, service agents, and service requesters.

The operator publishes the service to the agent

The requestor finds the required services through the proxy and binds them to the services

providers and requesters can interact

4. for applications that use the service, the process of using the service is completely loosely and transparently based on what technology is being developed, where it is, and what hardware platform the service is providing.

5. on the other hand, the service delivery system can be well reused without being invaded by other systems, and the evolution of the technology platform of the business system will not affect the business system using its services.

Part-3 "Enterprise Service Bus ( ESB) "

1. The definition of Enterprise service Bus (ESB) is usually as follows:

It is based on middleware technology and supports a set of infrastructure functions of SOA, it mainly realizes the transmission, transformation and routing of message, it is the backbone nervous system which connects Enterprise's various complex applications.

2. the different applications connected to the ESB are defined as different services (or components), and the interfaces between the services are defined in a neutral way, independent of the hardware platform, operating system, and programming language that implements the service.

3. through a well-defined interface and contract between these services, a variety of applications are combined in a loosely coupled way to connect applications and regulate message traffic at a reasonable pace that meets the needs of the business, thus achieving greater efficiency and reliability and faster response times.

Part-4 the SOA with the ESB the relationship "

1.SOA is an architectural model that links the different functional services (or components) of an application to a well-defined interface and contract between these services, which are used in a unified, common way to interact.

2.The ESB supports these service interaction capabilities and supports them by providing integrated communications, messaging, and event infrastructure.

3.The ESB provides SOA with an infrastructure that is consistent with the needs of the enterprise to provide the right level of service and manageability, as well as operations in heterogeneous environments.

4.An ESB is an intermediary for intelligent integration and management between services in an SOA architecture.

Part-5 "System Architecture Design"

1. under the SOA architecture idea, the business functions of the application system are encapsulated as services, providing standardized services externally through standard service intermediaries---Enterprise service Bus (ESB), applications that use services are also connected to the ESB, and the service is consulted and invoked by the ESB.

2. different technical agreements between service providers and service users, differences in data formats, and diversification of interactions are configured and processed through the service adapter (Adapter).

3. based on the above architecture core business system, credit management system, financial management system and other business systems encapsulated as a separate service, through the adapter and the ESB to connect to form a unified business process service platform.

4. Unlike traditional system integration methods, applications no longer need to consider and process differences with integrated applications.

5.as a bridge between services, theESB constructs a variety of interactive modes, such as request/response between services, publication/subscription of messages, event broadcast, etc., and also realizes the routing of messages, the distribution of messages, and the monitoring of messages.

Adapter undertook the translation between services, and completed the conversion between the interfaces of different application systems (for example, the payment system provides a message connection, the credit system is a Web service mode, By introducing adapter Two systems, the original interface can not be changed, thus ensuring the stability of the system.

Part-6 "Adapter (Adapter) Design "

1. After the introduction of the adapter, the application system is completely in accordance with the components of the design ideas to transform, only concerned about their own functions can be achieved, and external services and requests for services, external data and monitoring data.

2. This can be divided into "functional body" and "interface" two parts. The more emphasis is on the logically relatively independent and complete function, the interface is facing the adapter.

3. interaction with the ESB is given to the adapter (Adapter) for SOA integration based on the minimal cost of the original system transformation.

4. the adapters based on the above architecture are described below:

Adapter A

{

Incoming interface∥ External Request Service Interface

{

Ⅱ 1: ...;

Ⅱ 2: ...;

}

Outgoing Interface∥ interface for external services

{

OI1: ...;

OI2: ...;

}

∥function Part∥ Functional Implementation Section

}

Part-7 "Process Service integration"

1. through the unified Business Process service platform based on SOA, through the standardized process modeling, the bank separates the front, the middle and the background, and integrates them into the relationship of service provision and service usage.

2. The business process will consist of business functions, processes, business rules, human tasks and other components (e.g., approval in the loan opening process, account opening, etc.), which are organized in the form of services and grouped into business processes.

3. This creates a very flexible environment in which service components can be easily replaced.

For example, you can replace the human task approval component with a Business Rule service component, because the two services encapsulate its differences through adapter, with an interface consistency for the ESB, which does not have any impact on the process.

Part -8 "Summary"

1. Although SOA has a clear effect in achieving business agility, there are still problems with complex semantic definitions, degraded performance, reliability, and security in practical applications that need to be addressed in future studies.

SOA-based banking system architecture