A-Z Popular Blog Data Search »
Technology Guides

Why ESB Fails

 , updated on
Enterprise service bus, or ESB, is an architectural pattern and class of technology that puts an intermediary between data publishers and subscribers to simplify integration. Architecturally this makes sense. Under an ESB model, a publisher publishes its data or services via one interface and subscribers access data and services via one interface. This is significantly less complex than building interfaces between each and every publisher and subscriber that become a complex web of integration. Despite its architectural advantages, ESB can fail. When it does it is typically for one or two reasons:

Single Point of Failure

ESB introduces a single point of failure that may be less resilient than independent custom integrations. Sure, ESB platforms may be deployed in a highly scalable configuration with a large number of instances. However, if you're using a single ESB product that technology is a single point of failure. If a serious bug occurs, all an organization's integration flows may stop. This can become a mess as things queue up, transactions fail and things fall out sync.

Project Dependencies

Projects that can be handled by a single developer or team tend to be fast. With each additional team or set of specialized skills you add to a project, things tend to become slower, more expensive and more likely to fail. ESB is often handled by a special team and may be considered a specialized skill. As such, any project with an integration component requires the ESB team. This can be perceived as an overhead and project bottleneck that may be resisted.


This is the complete list of articles we have written about data.
Abstract Data
Atomic Data
Big Data
Cohort Analysis
Dark Data
Data Analysis
Data Architecture
Data Attribute
Data Cleansing
Data Collection
Data Complexity
Data Consumer
Data Control
Data Corruption
Data Custodian
Data Degradation
Data Dredging
Data Entity
Data Federation
Data Integration
Data Integrity
Data Liberation
Data Lineage
Data Literacy
Data Loss
Data Management
Data Massage
Data Migration
Data Mining
Data Owner
Data Producer
Data Quality
Data Remanence
Data Risks
Data Rot
Data Science
Data Security
Data States
Data Transformation
Data Uncertainty
Data Veracity
Data View
Data Virtualization
Data Volume
Data Wipe
Decision Support
Deep Magic
Empirical Evidence
Event Data
Hard Data
Information Assurance
Legacy Data
Machine Data
Market Research
Master Data
Misuse of Statistics
Personal Data
Personal Information
Predictive Analytics
Primary Data
Primary Research
Qualitative Data
Qualitative Info
Quantitative Data
Raw Data
Reference Data
Small Data
Soft Data
Source Data
Statistical Analysis
Statistical Population
Structured Data
Transaction Processing
Transactional Data
Types Of Data
Unstructured Data
If you enjoyed this page, please consider bookmarking Simplicable.

Data Integration

A list of data integration techniques.

Data Virtualization vs Data Federation

The difference between data virtualization and data federation.

Types Of Master Data

A list of criteria for deciding if something is master data or not.

Data Migration

The common approaches to data migration.

Data In Transit

A definition of data in transit with examples.

Data Architecture

The definition of data architecture with examples.


The definition of digitalization with examples.

Integration Examples

An overview of integration with examples.

Master Data

A definition of master data with examples.

Reference Data vs Master Data

The difference between reference data and master data.

Master Data Management

An overview of master data management.

Customer Data

A list of common types of customer data.

Data Examples

Common examples of data.

Data Collection

An overview of data collection with examples.

Unstructured Data

A definition of unstructured data with examples.
The most popular articles on Simplicable in the past day.

New Articles

Recent posts or updates on Simplicable.
Site Map