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.
On May 25th 2010, I attended the „FUSE Community Day 2010“ in Frankfurt, Germany. That is a free one day conference, where some important open source projects of Apache are presented by Fuse – a company which offers commercial support for versions based on these products.
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.