Welcome!

Server Monitoring Authors: Yeshim Deniz, Liz McMillan, Pat Romanski, Carmen Gonzalez, Ken Schwaber

Related Topics: IBM Cloud, Microservices Expo, Weblogic, Microsoft Cloud, Recurring Revenue, Artificial Intelligence, Log Management, Server Monitoring, Government Cloud

IBM Cloud: Article

ESB Pattern: What Is the ESB?

An ESB can mean vastly different things to different people

ESB products emerged around 2002 from message-oriented middleware (MOM). Faced with market domination by IBM, MOM vendors were the first to jumpstart the ESB concept with the aim of developing a unique selling proposition. They added Web service and EAI capabilities on top of existing message broker capabilities, and with analyst support coined the term ESB. ESB was positioned as a low-cost alternative to EAI and panacea for all integration needs - tell-tale signs of hype. Unfortunately, the standards community was too late to get on the bandwagon. In the absence of standards guidance and the lack of a clear definition, each vendor interpreted ESB to its advantage. As a result, comparing ESBs is like comparing apples and oranges. No two products are compatible today with severe consequences (in terms of vendor lock-in) for end users. SCA promises alleviation here, and market forces play in the favor of users too, with significant consolidation, convergence and commoditization taking place.

Pattern or Product?
An ESB can mean vastly different things to different people, and given the ESB market, most people think of ESB in terms of an ESB product with which they are familiar. The essence of an ESB can be much more easily grasped by talking about the ESB as a pattern: the pattern of applying an intermediate proxy to service communication. The ESB pattern is about performing integration tasks and adding value to client-service communication in an SOA - all completely transparent to the participants. As described in SOA Design Patterns, the ESB is a compound pattern that pulls together many enablement and enforcement capabilities that come in handy to the SOA practitioner (see figure below). Reliable Messaging, Message Manipulation, Data Format and Data Model Transformation as well as Protocol Bridging are just some sub-pattern examples under the ESB umbrella. These are all enablement aspects where the ESB allows communication between endpoints not possible otherwise. The ESB can also restrict communication and enforce policies relating to security (such as authentication and coarse-grain authorization), SLA Monitoring, Message Inspection, Intermediate Validation and Service Governance. Having said that, we treat ESB as a pattern and product type, synonymously.

Modern ESB vs. Traditional ESB
The traditional ESB was positioned as the enterprise integration backbone and as a fundamental building block for an SOA. Pundits touted the ESB as the "last middleware" that would gradually grow; instead of a big-bang replacement, segments would be added to the ESB, and applications added step-by-step until SOA bliss: i.e., every stove-pipe application exposed as a service on the ESB or on-ramped as a client. It was the easy path to SOA - or so it seemed.

However, the vision of a single-vendor, enterprise-wide and infinitely scalable integration backbone remained a pipe dream. Many enterprises soon had two or more ESB products in house that now needed to be integrated somehow; company-wide data models proved elusive.

The modern ESB accepts heterogeneity as a fact of life. It supports and embraces the Domain Inventory pattern. A domain is internally highly cohesive and externally largely autonomous from other domains. The ESB supports domain-internal communication by mapping protocols and connecting via adapters into legacy applications. Inter-domain communication does occur occasionally. The ESB can model the external "cell membrane" of the domain, exposing a select few endpoints to other domains. It can normalize these endpoints in terms of data model, protocol binding and security models, therefore simplifying inter-domain communication. The modern ESB is also lightweight, modular and builds on standards, such as SCA, to avoid vendor lock-in.

Alternatives
One obvious alternative to using an ESB is to not use one. "Smart" endpoints could communicate in peer-to-peer fashion and use a standard protocol for addressing all functional and non-functional capabilities (such as SOAP and WS*). All endpoints must then support the same data model and provide lots of capabilities. Consider reliable messaging: trapped messages, persistence, redeliveries, queue sizes, dead letter queues, etc., are just some aspects that must be controlled and monitored in a decentralized fashion. And this is just for the reliable messaging capability! David Chappell coined the term "application servers everywhere" and lamented the operational overheads associated with this approach. While smart endpoints can work if there are few of them, they can lead to uncontrollable service sprawl and spaghetti-connections in the long run. Malicious and invalid payloads can only be detected by the endpoint itself in this scheme - rarely a best practice and something discouraged by the Multi-layer Security pattern.

Another alternative is the provision of standalone infrastructure services. Integration capabilities are then implemented as and when needed (for example with a message broker). No investment in an ESB is necessary and no unused capabilities exist. When further requirements come up (such as transformation, protocol bridging, adapters, etc.) they can be provisioned with additional standalone infrastructure services. Again, such an approach can be very practicable in a small service portfolio. For larger deployments the installation, configuration and operation of the various standalone infrastructure services can become challenging. Frequently you want to combine various integration capabilities. The ESB can do so declaratively using the Microflow pattern - various integration aspects can be arranged, combined and modified in a very agile manner. Microflows are performant because of internal optimization (not every capability is a first-class service invocation). From a maintenance, agility and performance point of view, standalone infrastructure services therefore draw the short straw.

•   •   •

The SOA Pattern of the Week series is comprised of original content and insights provided to you courtesy of the authors and contributors of the SOAPatterns.org community site and the book "SOA Design Patterns" (Thomas Erl et al., ISBN: 0136135161, Prentice Hall, 2009), the latest title in the Prentice Hall Service-Oriented Computing Series from Thomas Erl (www.soabooks.com).

More Stories By Thomas Rischbeck

Dr. Thomas Rischbeck is an IT architect and business developer with [ipt], a local SOA consulting boutique with a Java technology focus (see Gartner's Guide to SOA Consulting). He has a track record of successful SOA introduction and delivery projects with a number of Swiss blue-chip clients. He specializes in SOA reference architectures, SOA design patterns and SOA security. Prior to joining [ipt] Thomas worked as an architect with Arjuna Technologies and Hewlett Packard Middleware Labs where he gained extensive experience in Web Services architecture and development.

Thomas holds a PhD in Parallel Computing from the University of Newcastle upon Tyne. He engages with the world-wide SOA community, is a frequent speaker and book author (co-author of "SOA Design Patterns" and "Modern ESB Architecture for SOA" within the Prentice Hall SOA Series).

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


IoT & Smart Cities Stories
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...