The world seems to be warming up to Business Process Execution Language, or BPEL. It's a specification with a lot of promise, and BPEL scripts will be the key to actually coupling (in a loose way, of course) Web services.
My blogmate Britton provides a great overview of Business Process Execution Language, or BPEL, in his recent post.
But BPEL has its issues, too, of course. Ronan Bradley, CEO of PolarLake, gives BPEL the frosty treatment in a recent post at WebServices.Org.
What's the problem with BPEL? Bradley says BPEL is far more limited in executing business processes than its name suggests. He warns against relying too much on a high-level solution such as BPEL for complex, down-and-dirty integration projects. "BPEL itself is not the danger, but the belief that BPEL in some way resolves all integration issues most certainly is," Bradley writes.
Bradley says BPEL "does not addressthe actual details of integration between diverse technologies and data models, and without these it cannot be the complete business process solution." BPEL won't help with the nitty-gritty, low-level work of unraveling spaghetti coding, for example.
Many people had high hopes for Enterprise Application Integration, but many EAI projects got mired in complexity, Bradley says.