Loading content
An Enterprise Service Bus (ESB) is an architectural concept for integrating heterogeneous applications using a central communication backbone that mediates, transforms, and routes messages. It provides standardized connectivity, message transformation, protocol bridging, and governance to decouple services and centralize integration logic. It is commonly use…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
An Enterprise Service Bus (ESB) is an architectural pattern that connects heterogeneous applications through a central mediation and transformation point.
The concept emerged in enterprise application integration and service-oriented architecture, when many different systems needed to interoperate through shared standards instead of numerous point-to-point links. Early industry literature attributes public use of the term to Gartner in 2002; Candle's Roma from 1998 is cited as an earlier commercial precursor. ESB later spread as a pattern for mediation, routing, and transformation in complex integration landscapes.
Think of an ESB as a central transfer hub for messages. Applications do not talk directly to each other; they hand messages to the bus. The bus receives them, validates them, transforms them when needed, routes them by rules or content, and delivers them over the right protocol to the target service. Cross-cutting concerns such as security, protocol bridging, error handling, and monitoring sit in the same place.
The bus accepts messages and passes them to the appropriate target service.
Rules, content, or metadata determine where a message is sent next.
Formats, data models, or headers are adapted to another system's expectations.
Different transport and communication protocols are connected through the bus.
Senders and receivers depend less directly on each other and can evolve separately.
Security, monitoring, versioning, and error handling can be applied in a more consistent way.
An ESB is useful when many legacy systems, partner services, or business applications with different protocols and data formats must work together and central rules for connectivity, transformation, and control matter. The trade-off is an extra platform layer: it can become a bottleneck or single point of failure, integration logic accumulates in one place, and operations plus troubleshooting become more complex. With only a few clear interfaces, direct integration is often simpler.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.