Skill Hub — Integration Architecture
Design, own, monitor, and fix integrations.
Practical working skills for integration architects and operators who need to make integration decisions, assign ownership, define contracts, handle failures, and build observability in SAP and mixed enterprise landscapes.
What this group covers
Integration Architecture skills bridge the gap between integration theory and operational reality. They help you decide between APIs and events, define who owns an interface, design error handling that actually works, and build monitoring that catches failures before business users do.
These skills are applicable to SAP-centric landscapes (IDoc, RFC, OData, AIF) and to mixed landscapes with cloud middleware, SaaS APIs, and event brokers.
When to use this group
- You are designing a new integration and need to choose a pattern, protocol, and contract.
- An existing integration fails repeatedly and no one knows who is responsible.
- You need to replace point-to-point connections with a more maintainable architecture.
- Business users report missing data before any technical alert fires.
- You are introducing events or APIs and need to define ownership, schema, and failure handling.
- A post-merger or platform consolidation requires an interface inventory and ownership cleanup.
Skills in this group
Interface Ownership
Assign clear ownership to every interface. Document who decides what. Prevent failures from sitting unresolved because no one is responsible.
API Integration
Choose the right protocol, define contracts, handle versioning, auth, and rate limits for REST, OData, SOAP, and SAP OData services.
Event-Driven Architecture
Decide whether an event should exist, who owns it, what its contract is, and how failures are monitored and handled.
Integration Observability
Design monitoring and alerting so failures are detected before business impact, and diagnostics are fast and repeatable.
Integration Error Handling
Design retry, dead letter, and escalation logic so transient failures recover safely and permanent failures escalate correctly.
Data Mesh
Apply data mesh principles to SAP and enterprise landscapes: identify domains, define data products, assign ownership, choose integration patterns.
Recommended path through this group
- Interface Ownership — Start here if your landscape has unclear responsibilities.
- API Integration — Use when designing or reviewing synchronous integrations.
- Event-Driven Architecture — Use when decoupling systems or replacing polling.
- Integration Observability — Use to build or improve monitoring.
- Integration Error Handling — Use to make integrations resilient.
- Data Mesh — Use for strategic data architecture and domain-driven data ownership.
How this group relates to other Skill Hub areas
- Architecture — System context mapping and architecture decision records provide the broader design context for integration choices.
- DAMA / Data — Data lineage, data contracts, and data quality skills feed into integration contract design.
- SAP AMS — Incident triage and root cause analysis skills are used when integration monitoring fires.
Status and limitations
This skill group is a public working interpretation of integration architecture practice. It is not official SAP, TOGAF, or vendor documentation. It focuses on operational applicability rather than comprehensive framework coverage. SAP-specific content is aligned with S/4HANA and common middleware patterns but may need adaptation for specific releases or custom landscapes.