Slides from my talk “How to choose the right Integration Framework” at JavaOne 2013, San Francisco, are online.
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.
Three integration frameworks are available in the JVM environment, which fulfil these requirements: Apache Camel, Spring Integration and Mule. They implement the well-known Enteprise Integration Patterns (EIP) and therefore offers 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 session shows and compares the three alternatives and discusses 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.
http://www.slideshare.net/KaiWaehner/spoilt-for-choice-how-to-choose-the
Data integration and workflow orchestration get confused because both ship hundreds of connectors. This post…
Process intelligence has become three things, not one: mining, orchestration, and a decision gate. Here…
AMQP, JMS, Kafka, and MQTT get compared as rivals, but a message broker, a log,…
Most vendors sell milliseconds, but most enterprise use cases do not need them. A critical…
Edge to cloud is not one integration problem. It is four: telemetry going up, control…
The Data Integration Landscape 2026 maps every major vendor across three communication paradigms: request-response, event-driven,…