Insights
Essays for post‑go‑live SAP BTP extension problems where architecture — not just implementation — is under question. References favor structural clarity over news or tutorials.
Core essays
Why BTP Projects Fail — The Boundary Model Every Architect Must Master
Introduces the Boundary Model and explains why failures surface at runtime boundaries months after go‑live.
Read →Why SAP BTP Identity Breaks Even When Everything Looks Correct
Identity propagation failures across layers despite correct configuration; where runtime context differs from design intent.
Read →Explore by boundary
Boundary
Identity
- Why SAP BTP Identity Breaks Even When Everything Looks Correct — Identity propagation failures across layers despite correct configuration; where runtime context differs from design intent.
Boundary
Tenant
- Inside SAP BTP — Multitenancy, CAP, Work Zone, S/4HANA Extensions, and AI — Builder-side analysis of multitenancy truth in BTP and why extensions must treat tenant boundaries as first-class architecture.
Boundary
Data
- Why SAP BTP Data Boundaries Break — And Why Extensions Fail Long After They “Work” — Data ownership and integrity drift at runtime causes post–go-live failures that code fixes cannot resolve.
Boundary
Integration
- The Integration Boundary — Integration jurisdiction at runtime differs from connectivity success; why governance must cross system edges.
Boundary
Lifecycle
- The Stability Window of BTP Extensions — Long‑term survivability depends on lifecycle boundary design, not just initial correctness.
Explore by real‑world symptom
Not every failure pattern is a bug
Many recurring SAP BTP extension failures are boundary and jurisdiction failures. Use the patterns to recognize the situation, then move to a decision.
See failure patterns → · Implementation vs verdict → · SAP BTP Architecture Review → · SAP BTP Extension Audit →
Prefer concrete, recognizable situations?
See Representative Cases — anonymized post‑go‑live cases that connect the model to live system reality.
Read by role
- CIO / CTO → Architecture Review · Strategic Boundary Verdict · Verdict Authority
- Lead Architect → Identity · Tenant · Data · Integration · Lifecycle
- Program Leadership → Full Boundary Audit · Ownership / jurisdiction map
- Security Architect → Identity propagation · Trust boundaries · Security hardening
- Integration Lead → Integration Boundary · Cross-system contracts
Full archive
- RISE Does Not Decide Your SAP BTP Extension Architecture — 2026-05-04 Why Clean Core Still Requires Architectural Judgment
- When a SAP BTP Extension Problem Stops Being a Delivery Problem — 2026-04-14 And Becomes an Architecture Judgment Problem
- Clean Core: The Architectural Reason SAP Never Fully Explained — 2026-03-24 Why Clean Core Is Not About Cost, Upgrades, or Best Practices — But About the Structural Survival of Enterprise Systems
- The Stability Window of BTP Extensions — 2026-03-03 Why Lifecycle Architecture Determines Long‑Term Success
- The Integration Boundary — 2026-02-03 Why Connectivity Is Not Integration
- Why SAP BTP Identity Breaks Even When Everything Looks Correct — 2026-01-20 Identity propagation failures across layers despite correct configuration; where runtime context differs from design intent.
- When CAP Forgets Its Boundaries - An Architect’s View from the Builder Side — 2026-01-08 CAP projects often pass unit and contract tests yet fail at runtime boundaries — identity propagation, tenant routing, and integration jurisdiction.
- AI-Generated Extensions on SAP BTP — 2025-12-15 AI accelerates code generation, but boundary correctness still determines whether extensions remain stable by tenant, identity path, and lifecycle over time.
- Why SAP BTP Data Boundaries Break — And Why Extensions Fail Long After They “Work” — 2025-12-09 Data ownership and integrity drift at runtime causes post–go-live failures that code fixes cannot resolve.
- Why BTP Projects Fail — The Boundary Model Every Architect Must Master — 2025-12-02 Introduces the Boundary Model and explains why failures surface at runtime boundaries months after go‑live.
- Why Even Single-Customer S/4 Extensions Must Use Multitenancy on BTP — 2025-11-28 Architectural Truth from the Builder Side
- Inside SAP BTP — Multitenancy, CAP, Work Zone, S/4HANA Extensions, and AI — 2025-11-25 An architect’s view from the builder side