In January 2015, I gave a talk about Enterprise Integration Patterns at OOP 2015 in Munich, Germany, reusing a talk from 2014 that had been updated with current trends to show how important Enterprise Integration Patterns (EIP) are everywhere.
It was great to see that Gregor Hohpe (founder / author of EIP book, and currently Head of IT at Allianz) was attending the session, too:
— Gregor (@ghohpe) January 29, 2015
Data exchange between companies increasing at a significant rate. Hence the number of applications which must be integrated increases too. The realization of these integration scenarios is a complex and time-consuming task because different applications and services do not use the same concepts, interfaces, data formats and technologies.
Enterprise Integration Patterns (EIP), first published over ten years ago by Gregor Hohpe and Bobby Woolf, has become the worldwide de facto standard for describing integration problems. It offers a standardized way to split huge, complex integration scenarios into smaller recurring problems. This session revisits EIPs and gives an overview about the status quo and its relevance regarding modern concepts such as Big Data, Internet of Things, Cloud or Microservices.
Fortunately, EIPs offer more possibilities than just being used for modeling integration problems in a standardized way. Several frameworks and tools implement these patterns, already. The developer does not have to implement EIPs on his own. Therefore, the end of the session shows different open source frameworks and proprietary tools available, which can be used for modeling and implementing complex integration scenarios by using the EIPs.
EIPs not just for ESB, but also for Streaming Analytics, OpenAPI, IoT and Microservices
As you can see in the slide deck, EIPs are not just important for “classical integration” using an integration framework such as Apache Camel or Spring Integration or an Enterprise Service Bus such as TIBCO BusinessWorks, IBM Integration Bus, Oracle Service Bus, Software AG’s WebMethods, MuleSoft ESB, Talend ESB, JBoss Fuse or WSO2 ESB. You also (have to) use EIPs with framework and tools for Stream Processing / Streaming Analytics (Apache Storm, Apache Spark, etc.), TIBCO StreamBase CEP, IBM InfoSphere Streams, Software AG’s Apama, etc.), API Management / Application Services Governance (TIBCO API Exchange, Apigee, SOA Software, etc.) and any other tool which uses “some kind of integration logic”, e.g. for Internet of things (IoT) or building business logic via Microservices.
Here’s the slide deck:
Integration will become even more important in the future than it is today!
The number of different data sources and technologies will increase at an unprecedented rate:
- CRM, ERP, Host, B2B, etc. will not disappear
- DWH, Hadoop cluster, event / streaming server, In-Memory DB – all of them have to communicate
- Cloud, Mobile, APIs, Big Data, Fast Data, Internet of Things are not optional, but our future!
Key message: EVERYTHING HAS TO BE INTEGRATED! Enterprise Integration Patterns help modeling and implementing all integrations.