SAP BTP Architecture Review
For SAP BTP extensions where implementation keeps moving but architecture can no longer be approved end-to-end. This is an independent review for boundary validity, jurisdiction, and decision clarity — not implementation takeover.
When this review is relevant
- The extension runs, but no team can legitimately approve the next change.
- Work continues, but the decision does not converge.
- AppRouter, Work Zone, CAP, XSUAA, destinations, or S/4 each appear locally correct, but the end-to-end behavior remains unstable.
- Rollout, onboarding, or security hardening exposes assumptions that should have been settled earlier.
- Vendor or team narratives conflict and no single owner can classify the failure.
What gets reviewed
In SAP BTP extension landscapes, these boundaries usually appear across AppRouter, Work Zone, CAP, XSUAA, destinations, HDI, S/4HANA integration, tenant onboarding, and lifecycle operations.
Runtime Boundary
Where behavior actually executes, how governed entry paths differ from direct testing, and which assumptions are only surviving on protected paths.
Identity Boundary
How identity, scopes, role collections, trust, and principal propagation behave across the chain rather than in isolated screenshots.
Tenant Boundary
Whether onboarding, subdomain routing, isolation, and subscription assumptions remain valid after the first successful context.
Data Boundary
Where truth lives, whether copied data is still governable, and whether ownership survives change across systems.
Integration Boundary
How released APIs, destinations, propagation modes, and system contracts behave under real operational constraints.
Lifecycle Boundary
Whether the extension can survive rollout, hardening, migration, parity drift, and future change without manual repair becoming normal.
What the review decides
- Whether the issue is still local implementation or already structural.
- Whether the current success path is representative or artificially protected.
- Which boundary is being weakened to keep the system working.
- What must change, what must remain, and who holds jurisdiction.
What this is not
- Not delivery rescue.
- Not SAP BTP implementation support.
- Not ticket execution.
- Not staff augmentation.
- Not a blame exercise.
What to send
A one-page summary is enough to assess whether the situation fits a fixed-scope review. If helpful, use the intake template rather than improvising a deck.
Boundary Model → · Implementation vs Verdict → · Failure Patterns → · Representative Cases →