|
|
What problems does BPEL help to solve?
Alexandre Alves's Blog |
September 16, 2005 12:47 PM
|
Comments (2)
There has been a lot of talk about BPEL, but mostly it is being focused on its technical features, such as how compensation handling works.
Particularly, I have not seen a lot of emphasis on the use-cases that BPEL helps to solve.
So, as an attempt to understand where one can use BPEL (in the context of integration) and what are the most valuable BPEL features, I've tried to come up with a (incomplete) list of scenarios where BPEL is able to help with:
- Intelligent dynamic routing based upon message content and process state;
- Compensation of non-transactional work and long-running processes;
- Sequential and concurrent splitter and aggregation of messages;
- Content enrichment and message filtering;
- Support for process instances with complex exception/fault paths;
- Support for process instances with multiple on-going conversations;
I would be very interested in knowing if anyone else has had experience implementing integration scenarios using BPEL. What were you trying to solve? What was easy to do and what was hard to do? How was it better (or worse) than using some other technology, such as XSLT?
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
Another question: Are peole bothered by the fact that the BPEL spec is not a standard?
Posted by: wgroth2 on September 17, 2005 at 12:58 PM
-
Personally, I haven’t seen a lot of concern regarding the fact that BPEL 1.1 is not a standard. Mostly I think this is so because there are still few _full_ adopters, hence those adopters are not yet worried about portability among BPEL engine providers. This will likely change when BPEL 2.0 is released as a standard sometime soon. So the next question is: will people adopt BPEL 2.0 promptly as it gets released?
Posted by: aalves on September 21, 2005 at 12:04 PM
|
|
