Welcome!

Microservices Expo Authors: John Rauser, Liz McMillan, Madhavan Krishnan, VP, Cloud Solutions, Virtusa, Jason Bloomberg, Pat Romanski

Related Topics: Microservices Expo

Microservices Expo: Article

Could Enterprises Be Pushing Back on ESBs?

Debate continues over messaging format viability

I just got back from the Gartner Application Integration show. This is perhaps the seventh of these conferences I attended, including the first one back in 1998. The good news is that the conference was packed and application integration seems to be making a strong resurgence with a little help from something called Web services. The bad news is that many of the attendees appeared confused, and the world of application integration and Web services/SOA seems more complex and difficult to grasp for the rank-and-file IT person than it was in the past. There don't seem to be as many clear answers these days, which is too bad because the problems seem to be getting bigger and integration is becoming a top-three IT priority according to the analysts.

The real surprise for me was the backlash against the concept of ESB (enterprise services bus) and its proper application within the enterprise as well as in the world of SOA. It seems to be falling off the current buzzword list as enterprises press forward with their SOA planning and implementation work, choosing more Web services?compliant messaging infrastructures instead.

In fact, I was most surprised to hear an analyst admit during a presentation that there was a flaw in the ESB concept, as end user organizations may over-integrate proprietary ESBs. This comment points to the fact that many ESBs will layer on top of existing messaging systems already in place, and may also be redundant with newer, more Web services?compliant approaches. In other words, you could end up with your traditional messaging system alongside your new ESB messaging system, as well as a new SOA infrastructure, all with redundant messaging capabilities.

The analysts could have a point there when considering the long-term strategic directions of SOAs. Indeed, many are calling ESBs "transitory" technology, something that will bridge enterprises to Web services, but perhaps not be the end solution.

Of course the ESB guys would argue that their ESB solution is indeed Web services/standards-based, albeit the underlying technology is based in Java or proprietary messaging systems. If you deal with the technology through standard interfaces, you should not be concerned with what happens behind the scenes. Moreover, they have all vowed to keep up with emerging Web services standards.

What's driving the debate even further is the appearance of new SOA infrastructure players with ESB-like capabilities, such as Blue Titan and their Network Director product with embedded queue technology in its Web services routers. Like the ESBs, they provide guaranteed message delivery, but they are also compliant with the current version of WS-ReliableMessaging.

The Essence of ESBs
I've heard the term ESB from both the analysts and vendors (both claiming ownership, by the way) to describe a technology stack that places service-oriented interfaces on top of messaging systems, such as JMS. Instead of invoking the Java interface to push and pull messages from a queue, you leverage a Web services interface. Going further, many of the ESB vendors have added "traditional EAI" features to their stacks, including transformation, routing, flow control, and process integration. Indeed, many have described ESB as kind of an EAI light.

Thus, those who employ an ESB would use it primarily for information-oriented integration, leveraging the ESB to move information between applications, which is traditionally the role of a messaging system. They also add transformation, routing, and other information brokering capabilities. However, most ESBs lack service- or behavior-based integration capabilities and the ability to effectively create and manage composite applications through this infrastructure. They do support simple orchestration, but again, typically around information movement.

The lack of true service-based integration is really the kicker for me when considering an ESB for use in an SOA. I believe the real value of creating an SOA and moving to Web services is the ability to reuse services inside and outside of an enterprise and create new applications by assembling services. This is how SOAs make you money. Also, SOAs provide us with the ability to create orchestration layers, abstracting services, and information flows for the purposes of creating business processes.

Thus, the purists are putting forth the argument that most SOAs should leverage pure Web services standards, otherwise integration and interoperability will be compromised. They further state that enterprises are going to double or triple up on messaging layers, implementing a JMS-based messaging system as well as a pure Web services?compliant messaging system at the same time. Moreover, ESBs typically exist with legacy messaging systems that are already in place. Furthermore, now that WS-ReliableMessaging is almost ready for primetime, as well as WS-Reliability (Sun's version, now ratified by OASIS), we're nearing the time when we can build Web services?compliant messaging systems without the need for an ESB. Thus SOA architects have other options today.

So, What's the Deal?
Clearly, building an SOA is one of the most confusing things to do these days. Not because the technology is so difficult to leverage; it's not, but there are many decisions to make, such as wading through competing technology as well as overlapping and numerous standards.

ESBs, at their essence, are reinvented messaging systems, but do have value for those who need messaging systems today and want tighter integration with their new service-based infrastructure. They do raise questions, however, as to their long-term value in light of newer, more Web services?compliant technology.

ESB vendors, however, are not going to stand around and watch their technology become irrelevant. Count on them to morph their product to meet changing expectations, including addressing emerging and existing Web services standards. Indeed, almost all ESB vendors have aligned with Web services standards, including WS-ReliableMessaging or WS-Reliability.

The key issue is that of fit. If you already have an existing enterprise middleware layer and are moving to service-oriented or Web services?compliant integration, leveraging an ESB is a step you may be able to skip. However, ESBs do seem to be a good fit for those enterprises performing simple information movement between stovepipes that don't need the heavy duty nature of more traditional integration technology. Once again, you have to map the appropriate technology to the problem, as well as consider longer-term strategic direction.

More Stories By David Linthicum

Dave Linthicum is Sr. VP at Cloud Technology Partners, and an internationally known cloud computing and SOA expert. He is a sought-after consultant, speaker, and blogger. In his career, Dave has formed or enhanced many of the ideas behind modern distributed computing including EAI, B2B Application Integration, and SOA, approaches and technologies in wide use today. In addition, he is the Editor-in-Chief of SYS-CON's Virtualization Journal.

For the last 10 years, he has focused on the technology and strategies around cloud computing, including working with several cloud computing startups. His industry experience includes tenure as CTO and CEO of several successful software and cloud computing companies, and upper-level management positions in Fortune 500 companies. In addition, he was an associate professor of computer science for eight years, and continues to lecture at major technical colleges and universities, including University of Virginia and Arizona State University. He keynotes at many leading technology conferences, and has several well-read columns and blogs. Linthicum has authored 10 books, including the ground-breaking "Enterprise Application Integration" and "B2B Application Integration." You can reach him at [email protected] Or follow him on Twitter. Or view his profile on LinkedIn.

Comments (1) View Comments

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.


Most Recent Comments
Javier Camara 02/10/05 04:12:33 AM EST

I agree in that the ESB concept is not fully sound. For me, a SOA makes sense if it is view as a constellation of web services interacting among them. For this, something like a UDDI server is required for each service locating each other.

For me, all this (i.e. services + directory) is just enough if only synchronous communications are used. If asynchronous communications are needed, then you need also publish/subscribe and store-and-forward, i.e. roughly what a MOM does. You can call it an ESB if you want, although I think this concept in the market encompasses several roles:
1. Publish/subscribe to messages
2. Store-and-forward messages
3. Route messages
4. Transform messages

An interesting thing to note is to implement points 1. and 2. you do *not* need business logic, while to implement 3. and 4. you do.

As I said, I see roles 1 and 2 required in SOAs with asynchronous interactions.

Roles 3 and 4 are also needed in many cases, mainly for integrating disparate systems. However, my main point against an ESB is that, in order to perform these roles, you do *NOT* need of a new, special concept like the ESB. *Any* service in the constellation of services can perform both routing and transformation. It can range from being a single component like an ESB (which I think is a bad idea), or it can just be a set of services (e.g. a different service performing specific adaptation for a system being integrated).

For me, using a single ESB for 3. and 4. breaks the beauty of the SOA idea. You are supposed to made all your data and business logic of your organization available as services in order to be reused, and suddenly you put on top an ESB in which you put *more* business logic (routing and transformation). So my point is that this should be implemented just by means of regular services, and not by specific, central-piece new components called ESBs.

Now, if for implementing routing and transformation you want to use Tibco, WebSphere or whatever, fine - however, the logic created by these products should be at the same level as the other services in the SOA, and not above.

So I am not saying that orchestrating tools are not useful. They are. Only, they are not *imprescindible*; and at any rate they should be viewed just as more services in the SOA. However, this does not fit the marketing strategy of ESB vendors which show its ESB as an *enabler* of a SOA, instead of just one more *component* of it.

@MicroservicesExpo Stories
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
Digital transformation has changed the way users interact with the world, and the traditional healthcare experience no longer meets rising consumer expectations. Enterprise Health Clouds (EHCs) are designed to easily and securely deliver the smart and engaging digital health experience that patients expect today, while ensuring the compliance and data integration that care providers require. Jikku Venkat