ESB Overview

Version 1 by Nicolas Salatge
on Jan 10, 2011 22:43.

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
Enterprise Application Integration (EAI) and Enterprise Service Bus (ESB) o ffer powerful integration solutions allowing service access. They are valuable architectures that expose services functions and allow their access. EAI appeared in the early 1990s through 2002s followed by ESB. While EAI proposes a centralized integration of services, ESB comes with a more decentralized and scalable envision. In the next section we discuss the service integration tools EAI and ESB.

*Service Integration Architecture*
The main goal of the EAI solutions is to provide integration of heterogeneous applications.
Both EAI and ESB share the same philosophy for achieving integration. The difference between them is that ESB address Web Services, is standard-based and distributed. The architecture of ESB and EAI middleware is almost the same.

ESB technology leverages best practices from EAI mechanisms and service oriented architectures. It is based on an open-standard message backbone dedicated to enable the implementation, deployment and management of SOA-based solutions. ESB technology exploits Web services paradigms, Message Oriented Middleware, smart message routing and transforming.

Enterprise Service Bus conciliate both Web Service concepts and service oriented architectures paradigms providing integration capabilities and deployment models. It supports a large number of services and high distribution and provides a capable, scalable and manageable integration infrastructure. ESB acts as a mediator between service providers and consumers basing key mechanisms:# First, services are discovered dynamically thanks to a common registry where service semantic description is stored and retrieved. The registry of the bus is technical as it stores the physical addresses of the services. The registry holds providers and requesters meta data.
# Second, business process and services are choreographed and orchestrated using a powerful orchestration engine. This engine is the corner stone mechanism of integration in ESB solutions.
# Third, communication between services and applications are fulfilled through XML native message. Messages are stored in a queue until their consumption by service clients. 
# Fourth, Mediation patterns are routing transformation, encoding and mapping. They insure the transformation of the message issued from an application to another application even if these are heterogeneous, its encoding and its mapping to the wright destination.

Web service mechanisms allow heterogeneous applications and services to communicate with the bus. These connectors support heterogeneous protocols SOAP/JMS, C applications, .Net, C++). As depicted in figure ESB allows connecting applications, data sources, customer portals, and B2B interactions.

                                                                                  !esb.png!

Remote applications integration is based on sophisticated mechanisms such as brokering; message transformation and routing, quality of service support, and service orchestration. Moreover, ESB offers a backbone implementation for service oriented architecture by connecting distributed services consumers with providers. The main functionalities of an ESB are supported by components that can be both centralized or distributed over a network. They make ESB a promising technological choice for Future Internet systems.