Objective and steps of the process

Our IT Integration Design guide aims to select and use Reference Blueprints to deliver the proper design of the IT integration flows.

Reference Blueprints align with Integration Domain, Integration Styles and Use-Case Pattern to offer detailed, prescriptive architectures. They help architects and integration teams design, implement, and standardise integrations using Integration's best practices.


Integration Platform  

→ The foundation where integration solutions are implemented, managed, and executed.


 Why This Matters

Structured Integration Approach → Ensures standardisation across the enterprise.
Predefined Use-Case Patterns → Reduces integration complexity by following Integration best practices.
Prescriptive Reference Blueprints → Provides guided architectures for each scenario.
Governance & Security → Ensures integrations are secure, scalable, and compliant.
Technology Alignment → Selects the right integration solutions "automatically" based on use cases.

📌 Reference Blueprints fit between Integration Domains, Integration Styles and Use-Case Patterns, ensuring integration is implemented using standardised integration architecture principles.

How These Works Together

🔹 Step 1: Identify the Integration Domain

🔹 Step 2: Select the Integration Style

🔹 Step 3: Choose the Use-Case Pattern

🔹 Step 4: Apply the Reference Blueprint

🔹 Step 5: Implement Using Integration Platform Technologies

Reference Blueprints

Reference Blueprints serve as the architecture backbone of the Integration design process, ensuring that Integration Domains and Integration Styles are implemented efficiently and securely.

They provide our IT projects with prescriptive guidelines to build scalable, governed, and efficient integrations.

They are all based on existing or validated Integration Components of the Integration platform.


Examples 


Examples
Integration DomainsCloud2Cloud, Cloud2OnPremise, OnPremise2OnPremise, User2Cloud, User2OnPremise, Thing2Cloud, Thing2OnPremise
Integration StylesProcess Integration, Data Integration, Event-Driven, User, Thing
Use-Case PatternsAPI-based Integration, Event-Driven Messaging, Data Replication, UI Integration, IoT Edge Processing
Reference BlueprintsCloud Integration Blueprint, Hybrid Integration Blueprint, B2B Integration Blueprint, Event-driven Integration Blueprint