Why is BPEL4WS better for a loosely coupled world than traditional workflow?

Why is BPEL4WS better for a loosely coupled world than traditional workflow?
Traditional workflow is primarily concerned with managing the distribution of work between people within a company. Over time, workflow has evolved to also engage in moving work between organizations, including those in separate enterprises.

BPEL4WS is an executable business process modelling language for expressing the logic of a composite Web service. BPEL4WS is specifically tailored for the loosely-coupled paradigm of Web services and is equipped with the ability to express comprehensive workflow patterns as well as communication patterns (e.g. request/reply, asynchronous). As such, BPEL is able to carry out complex workflow management tasks as well as handle enterprise integration tasks in various forms.

Web services composition and workflow management are related in the sense that both are concerned with executable processes. The advantages of BPEL4WS are that it is designed to fit within the Web services stack and hence ensures interoperability across implementations. A BPEL process is published using WSDL and is readily available for further consumption and interaction with other BPEL processes. BPEL4WS also provides for portability of the flow logic it expresses.
This was first published in July 2003

Dig Deeper on BPEL



Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.



Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: