camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Danny <>
Subject Camel EAI patterns vs. BPEL processes
Date Fri, 25 May 2012 19:16:46 GMT
How to choose?

I'll use orchestration as a generic term below that is synonymous with route
in camel 
and process in BPEL.

1. Orchestration of a series of web service calls. (WSDL and REST)
2. Orchestration engine must support asynchronous calls to an external web
3. Changes to the orchestration can be "hot deployed".
4. Ability to be able to run multiple versions of a particular
5. Support (or at least not the blocking of) The ability to abstract out of
orchestration engine the physical endpoints of services. 
(current thinking is with something like zookeeper)

We are currently leaning toward BPEL, but my fear is that it is to
heavyweight for 
what we need.  BPEL seems to be for overall business processes, like between 
multiple departments, with human interaction steps, various applications or
interfaces involved, etc.  Seems like overkill as we aren't (in general)
tying together a 
bunch of different enterprise applications. (CRM, Accounting, Finance,
Payroll, etc).

We need to "glue" together mostly internal web services to create an
efficient way for us to manage / change / monitor, etc 
this set of services, that taken together provide the revenue generating
ecosystem our customers pay us for.

We've found that BPEL meets the 5 above requirements (mostly), plus
monitoring is really already there as a web app 
(with the tool we are looking at), you can see the instances of processes in
real time, the data in the process, what step each is at, etc, etc.

But at the same time, when I look at the BPEL diagrams vs. the EAI diagrams
from the eclipse plugin for camel.
The camel EAI diagrams seem to fit much better than the BPEL ones with what
we are trying to do.

Is that feeling justified?  I realize this is highly subjective.

Thoughts or experiences are much appreciated.

Thanks for any feedback.

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message