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.
You are currently viewing a placeholder content from Default. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
ERP vendor selection for manufacturing is not a product decision. It is a strategic bet…
Process intelligence is not a single tool. It combines process mining, process orchestration, and a…
ERP modernization fails when the technology leads and the process work follows. Three German manufacturers…
Most organizations start their data governance journey by asking how to track where data comes…
Every enterprise is being told to go agentic. Meanwhile, the platforms holding your most critical…
AI agents fail in production when they are connected directly to raw event streams. Flink…