ABAP4C Cloud Deployment Pipeline — Architecture 2: Capella

Architecture Lab · Independent engineering prototype with bounded live execution evidence

ABAP Cloud deployment sometimes needs a dedicated control plane, local Eclipse bridge, bounded execution controls, receipts and recovery evidence rather than a direct tool invocation path alone.

Challenge

ABAP Cloud deployment sometimes needs a dedicated control plane, local Eclipse bridge, bounded execution controls, receipts and recovery evidence rather than a direct tool invocation path alone.

Architecture decision

Architecture 2 of the ABAP4C Cloud Deployment Pipeline capability: a Capella governed bridge with orchestration, policy controls, local Eclipse bridge, authenticated workspace, ADT repository discovery, RIS search, DDIC update, session handling, controlled retry, receipts and rollback references.

How it works

AI or Coding Agent → VS Code / Cline / Python → Capella Control Plane → Local Eclipse Bridge → ADT / RIS / DDIC execution → SAP ABAP Cloud → receipts, evidence and rollback controls.

Outcome and learning

Improve target-system variation handling and recovery evidence without claiming universal superiority over Architecture 1.