For organizations looking to streamline and simplify their infrastructure and support Service Oriented Architecture (SOA) initiatives, an Enterprise Service Bus (ESB) can be the answer.
What is an Enterprise Service Bus?
Unfortunately, this technology remains a mystery to many companies, and even the definition of an ESB can vary depending on who you talk to. This white paper attempts to clear up some of the confusion around ESBs and help your organization determine if this technology is needed to support your integration and SOA initiatives.
Understanding the ESB
Since gaining popularity in the last few years, ESB has become the subject of intense interest by enterprise customers and heated debate by technologists—a clear sign that the idea either carries significant merit or is compelling hype without substance. Certainly the noise level alone on ESB warrants an open-minded examination of the concept. Before diving into the technology, let’s first take a look at what an ESB is.
Defining the ESB
If you’ve done your research, you’ve probably seen that ESB can be described in a number of ways. After examining the most common definitions (below), it becomes apparent that these descriptions are actually pieces of a larger, composite definition that accurately describes this technology. An ESB:
- Is a backbone for integrating an enterprise’s applications and services
- Provides the necessary infrastructure to create a Service Oriented Architecture
- Is based on open standards such as XML, SOAP and WS-*
- Provides intelligent routing, such as publish-subscribe, message brokering, and failover routing
- Provides mediation and resolves security differences between endpoints
- Integrates with legacy systems using standards-based adapters
- Provides logical centralized management but is physically decentralized
- Able to monitor and throttle activity as per a Service Level Agreement (SLA)
Learn more. Download the White Paper now.