BPEL today can be used for simple orchestration of Web Services. It is primarily useful to technologists, rather than C-level executives. Use for BPM-like activities involving human interaction, forms processing etc. should be avoided as it is unclear exactly where this is going at the moment (although this may change with BPEL4People).
The basic process flow model of BPEL describes how a service interacts with one or more "partner links". This is most effective if you have a centralized hub-and-spoke view of the world, but in a highly distributed WAN based deployments you should beware of any BPEL implementation that requires that a process flow make a trip back across the network in between every step in the process.
In addition BPEL assumes that all services must be web services. With a pure BPEL solution there is no inherent support for legacy systems and relational data stores, and no built in support for mediation components such as transformation.
Dig Deeper on Topics Archive
Related Q&A from David Chappell
In this expert response, David Chappell discusses the quality of service functionality in WSDL 2.0 Continue Reading
In this expert response, David Chappell discusses how to go about matching up Enterprise Service Busses. Continue Reading
In this expert response, David Chappell discusses how much middleware latency is too much. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.