Inside a subaccount, where does the actual work happen?
Where do applications run?
Where do services live?
This is where environments come into the picture.
An environment in SAP BTP defines how and where applications are run.
A subaccount is your workspace.
An environment decides what kind of work you can do inside that workspace.
SAP BTP provides multiple environments because different applications need different runtimes.
SAP customers don’t all build the same kind of applications.
Some build cloud-native apps.
Some extend S/4HANA using ABAP.
Some work with containers and microservices.
Instead of forcing everyone into one model, SAP provides different environments, each suited for a specific purpose.
As an admin, we don’t need to master development in all environments.
But we must understand what each environment is meant for and when to enable it.
Cloud Foundry Environment
Cloud Foundry is the most commonly used environment in SAP BTP.
This is where:
-
most extensions are built
-
many services are consumed
-
applications are deployed and run
In Cloud Foundry, you’ll hear terms like:
-
Org
-
Space
-
Applications
-
Service Instances
As an admin, the key thing to understand is:
Cloud Foundry is the default and most flexible environment for running applications on BTP.
Kyma Environment
Kyma is based on Kubernetes and is used mainly for:
-
container-based applications
-
microservices
-
event-driven architectures
Kyma is powerful, but also more complex.
That’s why SAP does not enable Kyma by default in trial or paid accounts.
An admin has to explicitly enable it.
ABAP Environment
The ABAP environment is meant for customers and consultants who:
-
already know ABAP
-
want to build extensions using ABAP
-
want a cloud-based ABAP system
This environment feels familiar to traditional SAP developers, but it runs completely in the cloud and follows clean-core principles.
Comments
Post a Comment