This session is for SAP developers who are already working on, or about to start, a CAP-based application on SAP BTP and are facing architectural decisions that affect long-term stability.
This is the stage where things technically work, but are difficult to reason about.
Documentation no longer gives instructions.
Framework enforcement stops.
Responsibility shifts to you.
This session is relevant when you are facing situations such as:
• Unclear CAP service and domain boundaries
• Confusion between authentication and authorization behavior
• Inconsistent behavior across environments or deployments
• Uncertainty about where logic belongs (Fiori vs CAP vs BTP services)
A system that technically works, but feels structurally wrong and difficult to articulate
This is not a learning or training session.
There are no tutorials, demos, or step-by-step solutions.
This is a decision-framing discussion.
You bring a real project, design question, or architectural choice currently in play.
The session isolates assumptions, restores responsibility boundaries, and makes consequences explicit.
The outcome is structural clarity.
Ambiguity around ownership, enforcement, and responsibility is removed.