To ESB or Not to ESB?

Create a vendor selection project & run comparison reports
Click to express your interest in this report
Indication of coverage against your requirements
A subscription is required to activate this feature. Contact us for more info.
Celent have reviewed this profile and believe it to be accurate.
10 February 2009
Bart Narter


It is generally assumed that a service-oriented architecture (SOA) will have an enterprise service bus (ESB). Celent questions that basic assumption.

In this report, To ESB or Not to ESB?, Celent questions the baseline assumption that an enterprise service bus (ESB) is required for SOA. The vast majority of large banks have an ESB and there are many benefits that accrue to installing an ESB.

What isn’t as broadly discussed are the downsides of using an ESB and the other options available that are likely to be faster, less expensive, and perhaps no less flexible. The ESB also introduces a single point of failure (as shown below in Figure 1), processing overhead, and more complex audit trails.

Bart Narter, Senior Vice President of the Banking Group and author of the report states, “While the knee-jerk assumption is that to do SOA, a bank needs an ESB, it is possible that a bank could get more value from the SOA by not having one.” He continues, “However, working without an ESB requires a greater amount of discipline and coordination across the organization.”

A Japanese version of the report is also available.

Subscription required

Access to this content requires a Celent research subscription.

Subscribers should sign in to access this research.

If you are not a subscriber, register now or contact us to find out more about our subscription options.

Insight details

Corporate Banking, Retail Banking
Subscription(s) required to access this Insight:
Banking, >>Retail & Business Banking, >>Corporate Banking
Insight Format
Geographic Focus
Asia-Pacific, EMEA, LATAM, North America