SAP Cloud Platform – PaaS = (IaaS + PaaS + SaaS)

Share on facebook
Share on twitter
Share on linkedin





SAP Cloud Platform, are you confused? Don’t worry, I was too when I started reading about it. I couldn’t put it in one place either. It is too complex to be just called one thing. I will explain why, this is not a comparison of other solutions with SCP. In this blog, I will merely argue how powerful SCP is and what some of its features are. If I have to sum this up I would say SCP is Software as a service, Platform as a service and Infrastructure as a service. You might not agree with this now, but go with me for a second, I know officially it is called a platform as a service, which is what it becomes when all three of those things combine. Let us break this down and digest how this can be true.


Let’s start with the easier one, Infrastructure as a ServiceVirtual machines you can find yourself if there is need for it a virtual machine inside SCP, the plain old virtual machine just like the one you would find on AWS/GCP/AZURE with root privileges do with it as you will. One would argue, why is this a useful feature? Well, this could give one the access to securely connect/extend with other platforms/suite within the SAP secure network. i.e it could be used as a High-Availability extension for HANA system replication.

Platform as a Service, one of the biggest examples for this would be Cloud Foundry. SAP uses Cloud Foundry standards to use many IaaS and underlying infrastructure for Application runtimes. Using Cloud Foundry you would be able to build fast business applications, the agile way. As Cloud Foundry, says create Apps, not the platforms, any app any cloud – decoupled.

Besides the cloud foundry environment, SCP also provides Neo Environment which runs SAP propriety runtime. If you are looking for comparison follow this link here.

One other example would be a managed database service. These services are divided between the above-shared environments CF and NEO. Exclusively CF you will find PostgreSQL, Redis, RabbitMQ and Object Store while on Neo you will see SAP ASE, Document service and both environments have SAP Hana service. SADLY PostgreSQL and Redis are retiring from SCP.

SCP offers many other services which could be identified as PaaS, but let us move on. Software as a Service, just as PaaS, have many examples for this. I will try to pick the interesting ones. SAP Cloud Platform Enterprise Messaging service is found in the CF Environment and used for applications to communicate with each other asynchronously. Much like what RabbitMQ is used for.

Another Example would be Document Information Extraction, as the name suggests it extracts information from the document for example PDF and is automated, using API, it is fully automated. If I were to pick the third example I would suggest SAP Cloud Platform Identity Provisioning Service, used to manage the identity lifecycle processes whether it is cloud or on-premise.

So this undoubtedly proves our initial assumption that SAP Cloud Platform is actually PaaS = IaaS + PaaS + SaaS. We have merely scratched the surface with this. SCP is growing every day and SAP is working tirelessly in making it the more integral part of any business. If you have not explored it yet, go right ahead and see what it has to offer to you.  SAP Cloud platform has a number of capabilities available to make your business efficient in an agile way.