Skip to main content

What's Your ESB Got?

The ESB (Enterprise Service Bus), instant awesome integration power in a single tool. Magic SOA at the press of a single button. (Ok, maybe not but that's what the vendors say.)

An Enterprise Service Bus is an advanced middleware tool that serves multiple purposes to enable a managed SOA integration environment. If you're doing SOA, plan on getting one. And if you're doing SOA and you don't have one, you're not doing SOA - you're just using SOAP and XML for quick and easy point to point integrations.

So what does an ESB do for you?

• Communications and Protocol Transformation – The tool connects to systems providing a service or function one way, and allows systems requesting a service or function to communication another way. For example, the providing system may expose the function by MQ (IBM’s messaging protocol), while the requesting system may request via a SOAP (TCP/IP & HTTP). The ESB acts as the intermediary.

• Data Format Transformation – The providing system exposes the data in one format, the requesting system needs it in another format. Example, the providing system exposes it’s custom format record as a fixed length format. The requesting system needs to receive it in an XML format. The ESB performs the transformation (and provides a development environment for creating it, usually with a visual tool, quickly and easily.)

• Orchestration or Integration Workflow – This is the real power of an ESB. Combining multiple granular services into an integration workflow allows sophisticated multi-system processes to be quickly assembled in the ESB context. Such workflow may include sophisticated logic including things such as content based routing, the activation of appropriate transformations, protocols, processing, etc, and combine it all into a single sophisticated integration process.

• Messaging and Process Management – Not included in all ESB’s (or sometimes as additional components within the vendor suite), a messaging paradigm becomes of increasing importance as business processes spread across systems, with a corresponding decrease in reliability (simply because more systems are involved). Messaging and process management provide the integration space with the tools to compensate for and manage the cross-system processes.

With an ESB, the application developers no longer concern themselves with each individual system connection, dealing with different protocols and different data formats. The systems architect gains the ability to design ‘virtual’ operations that are composed of orchestrated web services bridging multiple systems. And all the individual steps required for doing so become reusable integration components (at least in the context of the ESB environment).

ESB - a must have for current generation multi-system and multi-business-process integration.

Popular posts from this blog

Integration Spaghetti™

  I’ve been using the term Integration Spaghetti™ for the past 9 years or so to describe what happens as systems connectivity increases and increases to the point of … unmanageability, indeterminate impact, or just generally a big mess.  A standard line of mine is “moving from spaghetti code to spaghetti connections is not an improvement”. (A standard “point to point connection mess” slide, by enterprise architect Jerry Foster from 2001.) In the past few days I’ve been meeting with a series of IT managers at a large customer and have come up with a revised definition for Integration Spaghetti™ : Integration Spaghetti™ is when the connectivity to/from an application is so complex that everyone is afraid of touching it.  An application with such spaghetti becomes nearly impossible to replace.  Estimates of change impact to the application are frequently wrong by orders of magnitude.  Interruption in the integration functioning are always a major disaster – both in terms of th
Read more

Solving Integration Chaos - Past Approaches

A U.S. Fortune 50's systems interconnect map for 1 division, "core systems only". Integration patterns began changing 15 years ago. Several early attempts were made to solve the increasing problem of the widening need for integration… Enterprise Java Beans (J2EE / EJB's) attempted to make independent callable codelets. Coupling was too tight, the technology too platform specific. Remote Method Invocation (Java / RMI) attempted to make anything independently callable, but again was too platform specific and a very tightly coupled protocol. Similarly on the Microsoft side, DCOM & COM+ attempted to make anything independently and remotely callable. However, as with RMI the approach was extremely platform and vendor specific, and very tightly coupled. MQ created a reliable independent messaging paradigm, but the cost and complexity of operation made it prohibitive for most projects and all but the largest of Enterprise IT shops which could devote a focused technology
Read more

From Spaghetti Code to Spaghetti Connections

Twenty five years ago my boss handed me the primary billing program and described a series of new features needed. The program was about 4 years old and had been worked on by 5 different programmers. It had an original design model, but between all the modifications, bug fixes, patches and quick new features thrown in, the original design pattern was impossible to discern. Any pattern was impossible to discern. It had become, to quote what’s titled the most common architecture pattern of today, ‘a big ball of mud’. After studying the program for several days, I informed my boss the program was untouchable. The effort to make anything more than a minor adjustment carried such a risk, as the impact could only be guessed at, that it was easier and less risky to rewrite it from scratch. If they had considered the future impact, they never would have let a key program degenerate that way. They would have invested the extra effort to maintain it’s design, document it property, and consider
Read more