Welcome!

Microservices Expo Authors: Liz McMillan, Elizabeth White, John Katrick, Pat Romanski, Karthick Viswanathan

Related Topics: Microservices Expo

Microservices Expo: Article

WS-BPEL 2.0: Not Backward Compatible?

Orchestration is a necessity

Let's face it, WS-BPEL 1.1 was not a great standard, and left so much out that many end users and vendors found it useless. In response, the vendors put a ton of proprietary extensions in their BPEL 1.1-based products, thus diluting its value to the point of "Why bother?" This was a dirty little secret in the world of SOA. Considering that BPEL 2.0 is on the horizon, I think it's time we began to talk about what's really there, how you can fix it, and what you need to do to get from point A to point B.

What's most frustrating about the issues here is that orchestration is indeed a core feature of SOA...the configuration component that makes orchestration that part of the architecture providing agility. Orchestration, at least the notion, is a necessity if you are building an SOA. It's the layer that creates business solutions from the vast array of services and information flows found in new and existing systems. Orchestration is a god-like control mechanism that's able to put our SOA to work, as well as provide a point of control. Orchestration layers allow you to change the way your business functions, as needed, to define or redefine any business process on-the-fly. This provides the business with the flexibility and agility needed, and is the core value of SOA.

Ranting
While I've been ranting and raving about this for some time, Dave Chappell does a much better job of explaining the limitations (from his blog www.davidchappell.com/blog/2005_11_01_weblog).

"Promoting BPEL's portability helps significantly in the first of these goals, since customers like the idea of not being locked in to a single vendor. But actually making customers successful has typically required extending BPEL in proprietary ways, which works against the language's promised portability. While BPEL purists might argue that all of these extensions should be provided via programming language-neutral web services interfaces, this isn't what's actually happening in the products."

With huge investments in BPEL by the larger SOA players out there, the dirty little secret is that BPEL 1.1 never really worked as advertised, and the amount of custom and proprietary extensions required to make the technology useful meant that the money, time, and effort was pretty much wasted if "standards and portability" were the goals.

The hype behind the standard, and the larger vendors supporting it, has really pushed the notion of BPEL in the last few years. However, those who have had to build solutions using the base 1.1 technology have run into many roadblocks, and thus the vendors have responded with their own unique extensions and toolsets. Are we employing a standard that's living and breathing, allowing us to protect our investment in our work, or just an instance of a vendor's tool? This is now a key question to answer.

BPEL 2.0
Enter WS-BPEL 2.0, and another opportunity for vendors to get BPEL right. You can find the draft specification on the OASIS site (http://docs.oasis-open.org/wsbpel/2.0/wsbpel-specification-draft.pdf), which I read, and discovered that this spec was much improved, but many issues still remain. For instance, there are considerable differences in WS-BPEL 2.0 compared to its previous 1.1 version. The major differences include syntax changes to the language, the inclusion of new features including parallel for-each, and modifications to the semantics of existing constructions, such as compensation handling. There are a few more, and I urge you to read both the 1.1 and 2.0 specs before diving into BPEL, or assessing how deep you're in already.

What if I already implemented orchestrations using BPEL 1.1, what do I do now? In short, you purchased Beta and the world is moving to VHS. I thought that this article by BEA's Alexandre Alves (http://webservices.sys-con.com/read/155617_1.htm) did a good job of summing things up.

"For all but the simplest business processes, migration from BPEL 1.1 to BPEL 2.0 is not an easy task. Some of the syntactic changes can be automated as shown [in the Alexandre Alves article], however the semantic differences, especially when dealing with links, messaging, compensation handling, and data manipulation, will demand a comprehensive and time-consuming process."

What bothers me most about this issue is not the fact that the standard, at least in some respects, is letting SOA down, but that orchestration is such a powerful need within SOAs, and there are few other alternatives that offer a better approach, standardized or not. Thus, end users who are tasked with building solutions using emerging SOA standards such as BPEL should begin to lean on their vendors now, as well as get more involved with their respective standards organizations.

I suspect the BPEL sales guys will get some angry calls around Christmastime from their users, perhaps more so considering the use of many proprietary extensions to get around the limitations of BPEL 1.1. Not a good way to start a standard. I guess that's why my old boss told me never to buy products until release 3.0.

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 (3) 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
Ron Ten-Hove 12/20/06 01:00:32 PM EST

There is no such thing as WS-BPEL 1.1. There is a rather poor proprietary specification, called BPEL4WS 1.1, which was submitted to the OASIS WS-BPEL technical committee (I am a member of that committee). BPEL4WS 1.1 was a starting point; given its many limitations and ambiguities, backwards compatibility was never a realistic option. Also, backwards compatibility of a public standard with a proprietary specification is rather absurd, unless that specification enjoys "de facto" standard status, which certainly isn't the case for BPEL4WS 1.1.

The members of the WS-BPEL TC at OASIS put together a lot of experience in the world of business process and workflow automation. A lot of work was put into making WS-BPEL better defined that BPEL4WS, to ensure portability of process definitions, and no need to resort to vendor extensions to perform tasks beyond the "hello world" level of complexity. In the process, many features of BPEL4WS were revised or replaced, in order to make the language more useful. Alexandre Alves was absolutely correct when he observed that conversion from BPEL4WS 1.1 would be challenging.

There is no doubt many applications running in a services-based environment will feature orchestration; we see this already with the use of BPEL4WS 1.X and other proprietary process languages in production environments, today. In fact, there are those who claim that the very definition of ESB must include orchestration.

Fred Holahan 11/13/06 04:15:39 PM EST

Dave,

You really need to develop some new material. This column is just a warmed over quacking of the two posts you made at InfoWorld back in September: http://weblog.infoworld.com/realworldsoa/archives/2006/09/wsbpel_20_not_... and http://weblog.infoworld.com/realworldsoa/archives/2006/09/more_on_the_bp....

Incidentally, citing Dave Chappell’s year-old blog post doesn’t help your credibility. Chappell’s assertion that “BPEL executable processes are likely to be of limited use” has already been proven wrong by numerous real world SOA applications that use BPEL for core orchestration.

BPEL is an open spec that is about to become a standard; it has no “dirty little secrets”. While it’s true that vendors have implemented extensions to make BPEL suitable for enterprise use, the same can be said for many (if not all) successful standards. Oracle extended SQL with PL/SQL, and Sybase did so with Stored Procedures, each of which is non-portable. Do those extensions render SQL itself worthless? Let me help you here … the correct answer is “no”. The essential value of any standard is knowledge portability. SOA Web Services Journal readers who made the investment to learn SQL will understand the enormous value of that investment, and the type of payback they can expect for the investment in learning BPEL.

With regard to migrating from BPEL 1.1 to 2.0, I will only say that we at Active Endpoints have made this migration automatic. You can open any 1.1 compliant process definition in the ActiveBPEL Designer and save it as a 2.0 process definition; all syntactic and semantic migration is handled automatically. The Designer is available for free download at http://www.active-endpoints.com/active-bpel-designer.htm.

Dave, you represent yourself as objective voice in the industry dialog surrounding BPEL. I find no such objectivity in your comments. The IT community deserves to have a complete, objective picture of BPEL as this critical standard reaches mainstream adoption. I’d suggest that you get on board to that reality.

Fred Holahan
Active Endpoints, Inc.

Steve Hoffman 11/06/06 08:51:56 AM EST

Still spreadin' the FUD, eh, Dave?

Please elaborate on your claim that "the dirty little secret is that BPEL 1.1 never really worked as advertised". Is there a specific functionality that the spec describes but implementations don't, or can't, support?

And what about those "alternatives that offer a better approach"?

It sure would be nice to see a little constructive criticism. Otherwise, you're bound to dismissed as just another counter-productive "naysayer".

Steve

@MicroservicesExpo Stories
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things ...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.
As people view cloud as a preferred option to build IT systems, the size of the cloud-based system is getting bigger and more complex. As the system gets bigger, more people need to collaborate from design to management. As more people collaborate to create a bigger system, the need for a systematic approach to automate the process is required. Just as in software, cloud now needs DevOps. In this session, the audience can see how people can solve this issue with a visual model. Visual models ha...
Containers are rapidly finding their way into enterprise data centers, but change is difficult. How do enterprises transform their architecture with technologies like containers without losing the reliable components of their current solutions? In his session at @DevOpsSummit at 21st Cloud Expo, Tony Campbell, Director, Educational Services at CoreOS, will explore the challenges organizations are facing today as they move to containers and go over how Kubernetes applications can deploy with lega...
Nordstrom is transforming the way that they do business and the cloud is the key to enabling speed and hyper personalized customer experiences. In his session at 21st Cloud Expo, Ken Schow, VP of Engineering at Nordstrom, will discuss some of the key learnings and common pitfalls of large enterprises moving to the cloud. This includes strategies around choosing a cloud provider(s), architecture, and lessons learned. In addition, he’ll go over some of the best practices for structured team migrat...