Implementing SOA with multiple ESB

As an ESB based SOA is implemented within a large organisation, it is inevitable that multiple (logical and physical) Enterprise Service Buses will be deployed. It is important to consider how these ESB's will actually be managed.

The mere existence of multiple ESB's introduce a variety of challenges related to architecture, configuration and monitoring. To complicate matters, the issue of ESB platform must be considered. What is the likelihood of all of the ESB's in a large organisation being implemented using a single product? The reality is that for a variety of reasons, multiple products are likely to be deployed. When developing an SOA strategy, it is wise to assume that there will be multiple ESB products deployed


Federated Enterprise Service Bus (ESB)The diagram shows a number of services and clients associated with 4 ESB's. The primary architectural question can be illustrated by considering how messages might be routed between a requester on ESB 2 and a service on ESB 3. The logical choices are:

  1. Client --> ESB 2 --> ESB 3 --> Destination Service
  2. Client --> ESB 2 --> Destination Service
  3. Client --> ESB 3 --> Destination Service

On the next page I will discuss some possible solutions to this important issue with ESB architecture

<<Previous 1 2 3 4 5 Next>>

© Web Wright Ltd