The API- and Event hub may support most of the integration needs. Certain data however may require a specific approach, for instance if the size, speed or format of data requires this, or an external party demands it.

Though Integration 2.0 does not explicitly mention Services or Service Oriented Architecture (SOA) it makes a clear distinction between stateful services -services that maintain specific data – and stateless services that don’t.

The Event and API hub are the central components in the integration landscape: In principle all communication will go through them. Besides loosely coupling EAC-s and processes it connects with other generic IT capabilities (functions) as well, like Master Data Management (MDM), Reference Data Management (RDM), Business Rule Management (BRM), Identity and Access Management (IAM) and Audit and Compliance Management. These all may provide functionality or data required by processes, EAC-s or each other. However, these services and EAC-s themselves are passive components other than publishing events that might be listened to by other components.

EAC-s may be integrated through their standard interfaces. API-s are centrally exposed to the enterprise though an API-hub. Events are exchanged from publishers to subscribers through an Event-hub.

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.