This is the second blog in a series of 6 blogs about integration 2.0. Read the first blog Integration 2.0!
These recent developments have urged us to define a new Integration approach, that we call “Integration 2.0”. This approach aims to address the challenges posed by the technical and business developments for the next decade.
Basically, the model is not far different from the current approach, but there are a few important changes.
Integration 2.0 is organized around “Enterprise Application Components” (EAC-s): applications or microservices that have been made autonomous. They provide their own generic interface and can operate independently from any other IT component.
Two mayor Integration capabilities are the backbone of the traditional part of the Integration 2.0 landscape: API-hub for (internal and external) synchronous communication and Event-hub for asynchronous communication.
A “process-hub” facilitates any process logic that exceeds the boundaries of EA Components.
In principle all main data exchange in the enterprise is over the API- and Event hub(s). Not only for EA Components, but also for generic IT capabilities (functions) like Master Data Management (MDM) and Business Rules Management (BRM). Also, business-to-business (B2B) communication is typically executed over the external API-hub.
Though additional capabilities may be required for specific domains, like Internet of Things (IoT), Business Intelligence and big data. The characteristics of the data to exchange like speed, volume and format exchanged require a dedicated approach.