This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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.
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.
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.