ESB Architecture Model

ESB Architecture Model

ESB is the intermediary between the client that calls the service and the provider of the service. It is responsible for handling the connection tasks between them, thus simplifying the client and the provider. IBM standards and opennessSource codeVice President Robert Sutor described in his blog eight defining principles that must be embodied in ESB:

• Versatility-- Provides a connection layer across the entire extended enterprise environment
• Heterogeneous-- Provides message-oriented multi-platform, multi-protocol, and multi-API support layers to integrate heterogeneous systems
• Interoperability-- Provides support for open protocols and supports interoperability between systems from multiple vendors
• Incremental Integration-- Provide the ability to dynamically expand the system as needed
• Service quality-- Provides various service quality, such as security, performance, reliability, and scalability.
• Replace-- Use open APIs to ensure that supplier implementations can be replaced
• Event locating-- Provides applications that will generate business eventsProgramAnd the ability to separate applications that submit and respond to these events
• Service Positioning-- Provides the function of separating applications by following the SOA design methodology and abstracting key functions as services.

At the technical level, these eight points actually indicate that the client should not directly communicate with the service provider, but the request should be routed through the message-and event-Oriented Middleware system, the Middleware system handles all the details, such as locating service providers, negotiating and integrating with service providers, and interacting with service providers.