These slides show and compare the three alternative integration frameworks Apache Camel (JBoss, Talend), Spring Integration (Pivotal) and Mule ESB, and discuss their pros and cons. Besides, a recommendation will be given when to use a more powerful Enterprise Service Bus (ESB) instead of one of these frameworks.
A question every customer asks me: How can you manage and monitor integration routes implemented with Apache Camel and / or Talend ESB (which is based on Apache Camel and also available as open source version). This blog post will show different alternatives to answer this question. The good news first: As Apache Camel and Talend ESB are based on open standards, you can use your own frameworks and tools if tooling of the product is not sufficient. So, I will not talk just about features of Apache Camel or Talend ESB, but also about additional options.
In February 2013, I was at ApacheCon NA 2013 in Portland, Oregon, USA. My session was named “Systems Integration in the NoSQL Era with Apache Camel”. I showed how to integrate several different NoSQL databases such as MongoDB (document), Neo4j (graph), HBase (column), AWS S3 (key-value), or Hazelcast (in-memory).
I had a talk at Java User Group Frankfurt (JUGF): “Showdown: Integration Framework (Spring Integration, Apache Camel) vs. Enterprise Service Bus (ESB)”. The room was fully packed, interest in integration frameworks, ESBs, and corresponding tooling is increasing every year! I uploaded the slides at Slideshare.
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.