Designing Resilient, Upgrade-Safe Extensions on SAP BTP

Keep this: job aid

Extension architecture review card

• Dependencies: released APIs and events first (Level A); any B or C justified, contained and dated.
• Keep a dependency register: version, state, level, owner, covering tests.
• Every remote call: timeout from the user's view, breaker per target, few retries with backoff, labeled fallback.
• Retry only random, transient failures of safe operations.
• Write down the regional resilience decision with the business owner.
• Each S/4HANA stack: contract tests and extension regression in test before production.
• Watch What's New and deprecations for every BTP service in the register.
• Structured logs with business key, correlation ids and outcome; symptom alerts with owners and runbooks.
• Review outcomes: approve, approve with conditions, revise; verify conditions at go-live.
• Record decisions as architecture decision records linked to the feature in SAP Cloud ALM.