This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Other Application Frameworks and the fly likes Camel, JBI, Mule .. which animal to pick? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Frameworks » Other Application Frameworks
Bookmark "Camel, JBI, Mule .. which animal to pick?" Watch "Camel, JBI, Mule .. which animal to pick?" New topic
Author

Camel, JBI, Mule .. which animal to pick?

Hussein Baghdadi
clojure forum advocate
Bartender

Joined: Nov 08, 2003
Posts: 3479

Hi,
It is nice to have Camel here in the Ranch.
I find it is really hard to decide when it is coming to choose integration software.
ServiceMix, Camel and Mule?
Some say JBI is the way to go, others swear by Mule.
If Camel is used by ServiceMix (I hope I'm not wrong) then why not to go with ServiceMix?
When to use the light weight Camel? and when to use the heavy weight Mule/ServiceMix?
Thanks for help and time.
Claus Ibsen
author
Greenhorn

Joined: Apr 01, 2004
Posts: 18
Hi John

The good thing is that you have choices.
Although you then have to do your assessment.

In terms of JBI, I see that as legacy now. I suggest only to use JBI if you have experience or have existing JBI components you need to leverage.
There is a good blog here about JBI
http://trenaman.blogspot.com/2009/08/camel-vs-jbi.html

Apache ServiceMix is an ESB which ships with Camel out of the box. Camel is the light weight routing engine inside ServiceMix.
Apache ServiceMix is the server (it has start/stop scripts etc.). This is a very good fit. ServiceMix allows you to deploy and run your Camel apps.

I suggest to start out with Camel, its often the most easy to get started with. Do some prototyping. Camel is so agile and flexible
that you can run it inside the server you pick. Whether that is ServiceMix, Tomcat, WebSphere etc.

At Camel we have a link collection you can take a look at, some of the links may talk about this topic
http://camel.apache.org/articles.html


In terms of Mule then I am biased towards Camel and will let the Mule people speak for themselves.
However I suggest to listen to the Basement coders podcast about Camel. Link to this is from the link above.
You got some hints what they see being picked out there in real life.


Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Padmarag Lokhande
Ranch Hand

Joined: May 29, 2008
Posts: 93
I have used Mule ESB and OpenESB in Netbeans and can tell that OpenESB is good if you have a lot of SOAP WebServices.
OpenESB is BPEL centric.

MuleESB is also good and has integration with lot of protocols.


- Padmarag Lokhande
SCJP5 - http://blog.padmarag.com
 
 
subject: Camel, JBI, Mule .. which animal to pick?