[Introduction to ESB theoretical knowledge]

The full name of ESB is Enterprise Service Bus, that is, Enterprise Service Bus. It is the product of the combination of traditional middleware technology and XML, Web services and other technologies. ESB provides the most basic connection center in the network and is a necessary element to build the nervous system of the enterprise. The emergence of ESB has changed the traditional software architecture and can provide a cheaper solution than traditional middleware products. At the same time, it can also eliminate the technical differences between different applications, let different application servers operate in coordination, and realize the integration of different services. communication and integration. From a functional point of view, ESB provides event-driven and document-oriented processing modes, as well as a distributed operation management mechanism, it supports content-based routing and filtering, has the ability to transmit complex data, and can provide a series of standard interfaces .



 

 

 

Basic Concepts of ESB

Enterprise Service Bus (ESB) developed from Service-Oriented Architecture (SOA) and is the product of the combination of traditional middleware technology and XML, Web services and other technologies.

ESB provides the most basic connection center in the network and is a necessary element to build the nervous system of the enterprise. ESB adopts a "bus" model to manage and simplify the integration topology between applications, based on widely accepted open standards to support dynamic interconnection between applications at the level of messages, events and services, It is a standard way of integrating between loosely coupled services and applications. It can act on:

① Service-Oriented Architecture - Distributed applications consist of reusable services;

②Message-oriented architecture - sending and receiving messages between applications through ESB;

③ Event-driven architecture - asynchronously generate and receive messages between applications.

The emergence of ESB has changed the traditional software architecture, and can provide a cheaper solution than traditional middleware products. At the same time, it can also eliminate the technical differences between different applications, let different application servers operate in coordination, and realize the integration of different services. communication and integration. From a functional point of view, ESB provides event-driven and document-oriented processing modes, as well as a distributed operation management mechanism, it supports content-based routing and filtering, has the ability to transmit complex data, and can provide a series of standard interfaces .

 

 

 

basic skills

1) MetaData management of services: Manage the registration, naming and addressing of services within the bus category.

2) Transport Services: Ensures the correct delivery of messages between business processes interconnected via an enterprise bus, and also includes content-based routing capabilities.

3) Intermediary: Provide location-transparent routing and positioning services; provide a variety of message delivery forms; support widely used transmission protocols.

4) Multi-service integration methods: such as JCA, Web service, Messaging, Adapter, etc.

5) Service and event management support: record, measure and monitor data for calling services; provide event detection, triggering and distribution functions;

 

 

extensions

1) Service-oriented metadata management: He must understand the two ends mediated by him, that is, the service request and the requester's requirements for the service, as well as the service provider and the description of the service he provides;

2) Mediation: It must have some mechanism to complete the role of mediation, such as protocol conversion;

3) Communication: publishing/subscribing of services, responses/requests, synchronous/asynchronous messages, routing and addressing, etc.;

4) Integration: legacy system adapters, service orchestration and mapping, protocol conversion, data conversion, continuation of enterprise application integration middleware, etc.

5) Service interaction: Service interface definition, replacement of service implementation, service message model, service catalog and discovery, etc.

6) Service security: authentication and authorization, non-repudiation and confidentiality, support for security standards, etc.;

7) Quality of service: transactions, deliverability of services, etc.;

8) Service level: performance, availability, etc.

The two most frequently mentioned functions in ESBs are message transformation and message routing.

 

 

Application Features

Large-scale distributed enterprise applications require relatively simple and practical middleware technology to simplify and unify the increasingly complex and cumbersome enterprise-level information system platform. Service-Oriented Architecture (SOA) is the ability to link different functional units of an application through well-defined interfaces and contracts between services. SOA enables users to reuse software without restrictions and interconnect various resources. As long as IT personnel choose standard interfaces to package old applications and build new applications into services, other application systems can easily use these features.

The key to underpinning SOA is its messaging architecture - the Enterprise Service Bus (ESB). ESB is the product of the combination of traditional middleware technology and XML, Web services and other technologies, and is used to achieve accurate, efficient and secure delivery of different messages and information in enterprise applications. Let different application services operate in coordination to achieve communication and integration between different services. ESB has a very wide range of uses in different fields:

Telecom field: ESB can fully support the application integration concept of OSS in the telecom industry. It is an ideal carrier-class application software carrier platform.

Electric power field: ESB can fully support the data integration concept of EMS in the electric power industry, and is an ideal SCADA system data exchange platform.

Financial field: ESB can fully support the process integration concept of business processing platform between banks and enterprises, and is an ideal B2B transaction support platform.

E-government: ESB can fully support the platform realization of e-government application software business basic platform, information sharing and exchange platform, decision analysis support platform and government affairs portal.

 

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326655387&siteId=291194637
ESB
ESB