• 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
  • Ron McLeod
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Rob Spoor
  • Devaka Cooray
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Jj Roberts
  • Al Hobbs
  • Piet Souris

which ESB to choose for integration

 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Bartender
Posts: 1316
39
IBM DB2 Netbeans IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
+ 1 for Mule ESB as Claude mentioned the IDE is very useful.

Regards,
Luis
 
Ranch Hand
Posts: 10198
3
Mac PPC Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Apache Camel is not an ESB but rather an integration platform. Apache Camel together with Apache ServiceMix makes it an ESB.

I came across this comparison: https://www.mulesoft.com/resources/esb/mule-vs-camel-comparison


Personally I would prefer Apache Camel and ServiceMix as my ESB stack which has backing from RedHat!
 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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.
 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Ranch Hand
Posts: 104
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 !
 
reply
    Bookmark Topic Watch Topic
  • New Topic