21.5 Enterprise Integration Architecture
Enterprise Datasphere rarely has one integration pattern.
Pattern selection
| Pattern | Prefer when |
|---|---|
| Federation | Fresh source access is important and source/runtime constraints permit |
| Replication | Local persistence improves reliability or workload behavior |
| Transformation | Data must be materially reshaped or harmonized |
| Semantic onboarding | SAP semantic objects should be brought into Datasphere |
| Data products | Governed reusable datasets should be consumed across boundaries |
SAP landscape
Typical sources include:
S/4HANA -> Datasphere
BW/4HANA -> Datasphere
BW Bridge -> Datasphere
Non-SAP landscape
Typical patterns include databases, cloud warehouses, object storage, APIs and partner data.
Integration architecture questions
For each source document:
- extraction method
- initial load
- delta strategy
- latency
- source impact
- failure behavior
- reconciliation
- ownership
- security
- expected growth
Architect principle
Do not select an integration mechanism because it is familiar. Select it because it satisfies the workload contract.