Integration styles represent key integration archetypes, which describe how an integration scenario between a business application and its target is realized.
Each integration style is refined by use-case patterns, which describe frequently used integration use-cases
Based on the same principles, cross-use-case patterns complement one or more of the five core integration styles (such as “API-managed integration” or “event-based integration.”)
The current version of our Integration Design Framework includes five integration styles, which are:
All integration styles are technology agnostic and are applicable within multiple integration domains.
Process integration | Data integration | Analytics integration | User integration | Thing integration | |
Objective | Chaining of business processes | Synchronization of data | Deriving business insights from business applications and data sources | Omni-channel access to back-end applications | Capturing and processing of real-world data |
Interaction type | System-2-system | System-2-system | System-2-user | User-2-system | Thing-2-system |
Coupling to application | Process-level | Data-level | Data-level / business-level | User interface level | Thing event |
Primary trigger | Application event | Schedule or application event | Application event (or User event) | User event | Thing event |
Execution mode | (Near) real time | Batch or near real time | (Near) real time or batch | (Near) real time | (Near) real time or batch |
Unit of data exchange | Single objects | Bulk-data or single objects | From aggregated to line-item data | Single objects or bulk-data | Single objects or bulk-data |
Specific requirements |
|
|
|
|
|