Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 7: The Enterprise Service Bus - Coggle Diagram
Chapter 7: The Enterprise Service Bus
ESB
ALLOWS YOU TO USE SERVICES IN A
PRODUCTIVE SYSTEM
ESB Responsibilities
providing connectivity
Data transformation
(Intelligent) routing
Dealing with security
Dealing with reliability
Service management
Monitoring and logging
ESB Differences
ESB might consist of several tools and programs that run centrally, and/or decentrally and are used by service designers, implementers, and operators.
Point-to-Point
If the consumer has to know the endpoint, it sends each request to a specific receiver. Call fails if physical receiver is not available.
Mediation
consumer does not have to know the endpoint of the provider
identifies the provided service by a tag or symbolic that the ESB interprets to find an appropriate provider
ESB plays the role of a mediator or broker, which leads to a loosely coupled infrastructure
Interceptors
ESB based on a point-to-point protocol can support indirect service calls is by providing so-called "interceptors" or "proxies
An ESB with a load balancer for provided services
Complicated ESB approach provides an interceptor or proxy for each provider and for each consumer
consumer will communicate in a "point-to-point" fashion only with its specific interceptor
interceptor will route each call to the appropriate provider, using its specific interceptor.
Protocol-Driven
ESB defines a protocol, and the providers and consumers send and receive messages according to this protocol
Exp:
Web
Services, which require a SOAP protocol
API-Driven ESB
ESB defines platform- specific APIs (such as Java interfaces), and the providers and consumers use these APIs for service implementations and service calls
solution might not involve any specific tool or piece of software at all