BTP Fundamentals Part 2: Runtime Environments and Connectivity
Choose where code runs and how it reaches back-end systems: Cloud Foundry for buildpack-based apps, Kyma for Kubernetes workloads, the ABAP environment for ABAP cloud development, and the Cloud Connector plus Connectivity and Destination services for secure on-premise access.
Explanation
📌 KEY POINTS
✅ Cloud Foundry: push apps with buildpacks (Node.js, Java, Python); simple scaling and service binding.
✅ Kyma: managed Kubernetes for containers, microservices and event-driven workloads.
✅ ABAP environment: ABAP Cloud development on BTP (RAP), close to S/4HANA skills.
✅ Cloud Connector creates an outbound, secure tunnel from the on-premise network to BTP; apps use it via destinations.
⚠️ Choosing a runtime by trend instead of team skills and operational needs creates long-term cost.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 mapped BTP. Now runtimes and connectivity.
━━━━━━━━━━━━━━━━━━━━
▶ 1. CLOUD FOUNDRY
- Orgs/spaces, cf push, buildpacks, services.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 2. KYMA\n• Kubernetes namespaces, containers, APIRules.
━━━━━━━━━━━━━━━━━━━━
▶ 3. ABAP ENVIRONMENT
- RAP, ABAP Cloud, released APIs.
━━━━━━━━━━━━━━━━━━━━
▶ 4. CLOUD CONNECTOR
- Installed on-premise; outbound connection; access control.
━━━━━━━━━━━━━━━━━━━━
▶ 5. CONNECTIVITY & DESTINATIONS
- Apps call on-premise via destination with proxy type OnPremise.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Compare runtimes for one use case.
- Install/check a Cloud Connector in a sandbox.
- Create an OnPremise destination and test it.
✅ CHECKPOINT: an app reaches an on-premise system via Cloud Connector.
Code example
===== RUNTIME CHOICE =====CAP Node.js/Java app, simple ops → Cloud FoundryContainers, microservices, custom K8s tools → KymaABAP skills, RAP extensions → ABAP environment ===== ON-PREMISE PATH =====BTP app → destination (proxy type OnPremise, location ID) → connectivity service → Cloud Connector (on-prem) → S/4HANA / ECCCloud Connector: subaccount connection, virtual host mapping, allowed resources (paths)Real project scenario
A mid-size company built a side-by-side extension in Kyma although the team only knew ABAP and Node.js. Operations struggled. Moving the app to Cloud Foundry with CAP simplified deployment and support.
Common mistakes
- Runtime by trend.
- Inbound firewall openings.
- Exposing all paths in Cloud Connector.
- Ignoring team skills.
- No destination governance.
Best practices
- Choose by skills and needs.
- Use Cloud Connector.
- Expose only needed resources.
- Standardize runtimes.
- Govern destinations.
Interview angle
Questions: "Cloud Foundry vs Kyma vs ABAP environment?", "What is Cloud Connector?", "How does an app reach on-premise?"
Strong answer: runtime traits and choice criteria, Cloud Connector, connectivity/destination flow.
Practice this lesson
Quick check
1. What is the primary purpose of a role collection in the SAP BTP security model?
2. What is the main role of the Authorization and Trust Management service (XSUAA) in SAP BTP applications running on Cloud Foundry?
3. Which statement correctly describes how SAP BTP supports multiple runtime environments such as Cloud Foundry, Kyma, and ABAP?
Interview questions
1. What are the differences between CAP and RAP, and how should a developer choose between them?
Answer it in your own words first, then compare.
2. How does BTP handle security using Identity Authentication Service (IAS), XSUAA, and Role Collections?
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.