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 very interesting talk at OOP 2013 in Germany. OOP is a great conference for software architects and decision makers. The topic of my talk was “Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)”. Hereby, I want to share the slides with you…
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.
This week, I was at CamelOne 2012 in Boston, organized by FuseSource. Sessions covered several open source projects such as Apache Camel, Apache ServiceMix, Apache ActiveMQ, and Apache CXF. Attendees learned directly from their peers and other industry experts how open source can deliver measurable technical and business benefits to their organizations.
Data exchanges between companies increase a lot. The number of applications, which must be integrated increases, too. The interfaces use different technologies, protocols and data formats. Nevertheless, the integration of these applications shall be modeled in a standardized way, realized efficiently and supported by automatic tests. Such a standard exists with the Enterprise Integration Patterns (EIP) , which have become the industry standard for describing, documenting and implementing integration problems. Apache Camel  implements the EIPs and offers a standardized, internal domain-specific language (DSL)  to integrate applications. This article gives an introduction to Apache Camel including several code examples.
Three lightweight integration frameworks are available in the JVM environment: Spring Integration, Mule ESB and Apache Camel. They implement the well-known Enteprise Integration Patterns (EIP, http://www.eaipatterns.com) and therefore offer a standardized, domain-specific language to integrate applications.
These integration frameworks can be used in almost every integration project within the JVM environment – no matter which technologies, transport protocols or data formats are used. All integration projects can be realized in a consistent way without redundant boilerplate code.
This article compares all three alternatives and discusses their pros and cons.
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.