• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Tim Cooke
  • Jeanne Boyarsky
  • Liutauras Vilda
Sheriffs:
  • Frank Carver
  • Henry Wong
  • Ron McLeod
Saloon Keepers:
  • Tim Moores
  • Frits Walraven
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Himai Minh

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

 
clojure forum advocate
Posts: 3479
Mac Objective C Clojure
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
author
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

 
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
For my next trick, I'll need the help of a tiny ad ...
Garden Master Course kickstarter
https://coderanch.com/t/754577/Garden-Master-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic