Enterprise Service Bus (ESB)(Chapter 9).ppt

Enterprise Service Bus (ESB)(Chapter 9) B. Ramamurthy The concept of bus Consider a hardware bus: connects chips of different functions and from different vendors Now imagine a software bus: a standardized way of hooking together any software components; examples OMG’s CORBA (synchronous) EJB in J2EE (synchronous) IBM’s MQSeries (asynchronous) Tibco’s Rendezvous (asynchronous) Types of ESB Ideal software bus supports a single communication model (fig.9.1). A software bus may also support various communication models at the same time (fig.9.2): synchronous, asynchronous, and file-based. The infrastructure of a real-world enterprise will normally consist of various products that support similar communication models. An enterprise is a meta bus that supports various products and technologies of the enterprise Example: Credit Suisse uses a synchronous information bus, an asynchronous event bus infrastructure and a file transfer-based bulk integration infrastructure driven by application which in turn are driven by business demands. ESB Functions Stub/dispatcher code generation (development) Execution container functions (deployment) Logging and auditing (runtime management) An important item is missing in the text: provisioning Availability and scalability Securing an SOA Service stub and dispatcher Execution containers Application servers Server farms Generic features set of an execution container are: Dispatching and servicing Transaction management Security Logging Billing Systems management functionality Message transformation Cross-container integration Execution containers provide a rich set of functionality that makes deployment and management of individual services reasonably straightforward. However the key challenge of an enterprise SOA is to define an architecture that enables applications to use different services independently of their container. Challenges are: interoperability including transactionality and security Solution: in a system where services