I would like to know which architecture to choose - Apache Camel or Mule soft for a ESB setup.. We have a large transaction based enviornment with large number of user transactions happening.
ESB should well be integrated with other products too such as SAP, Salesforce etc..No cloud based setup or Hadoop/Big data kinda technologies used..
Times ago I tried Mule ESB. I preferred it among other open source solutions most because it has a good IDE - Mule Studio, now Any point studio - and I hate working directly with XML... Which I had have to do with Camel.
Under the hood, I think they have a lot of similarities, for example about framework internally used.
sowjan kumar wrote:I would like to know which architecture to choose - Apache Camel or Mule soft for a ESB setup.. We have a large transaction based enviornment with large number of user transactions happening.
ESB should well be integrated with other products too such as SAP, Salesforce etc..No cloud based setup or Hadoop/Big data kinda technologies used..
Thanks
I recommend Jboss Fuse ESB. It has Apache Camel and Active MQ embedded in it and other option would be WSO2 ESB. This requires more support from the WS02 technical team to work extensively.
Mule ESB is best choice in your case and Mule ESB provides Cloud Connect technology, which can be used along with the SAP-certified connector to integration with Salesforce’s APIs. With Mule ESB, integration between SAP and Salesforce is not much easier.
Look for mule sites for if there are any limitations too.
I would consider following "few" aspects to choose an ESB product
- Product extensiability
- How far product can integrate within current infrastrucutre (several end point connectors like SAP, SFDC, CICS.., supported dataformats XSD,CSV, IDOCS, Copybooks..)
- Non-functional aspects like supported secutiry mechanisms, transactions
- How quicly and easily solutions be implemented e.g. graphical coding is prefereable
- Performance and Runtime governance capabilities
- Operation and maintenance cost
- Knowledge available internally with in org. and external to org.
- Atleast try to do a reference check with other partners who are already using a proposed ESB solution..
- Vendor support..
No matter if ESB is open source or commercial. In my view total cost of owenrshi for both are same !
Regards, Sujeeth Pakala
SCJP, SCWCD, SCBCD, ICAD, XML Master Basic, Certified SOA Professional
I'm not sure if I approve of this interruption. But this tiny ad checks out:
a bit of art, as a gift, the permaculture playing cards