Beyond SAP Cloud - Episode 9: BTP Runtime Strategy

[WouterLemaire]

This episode explores BTP runtime strategy, discussing the different types of runtimes available: Kyma, Cloud Foundry and ABAP. Kyma, based on Kubernetes, runs on-demand, offering flexibility and cost-effectiveness for use cases that don't require to be up and running 24/7. Cloud Foundry is ideal for always-on applications, while ABAP may be more suitable for large-scale, enterprise applications. The choice of runtime depends on factors like developer skills, company policies and the scale of applications to be built. Companies must evaluate their needs to determine the best runtime for their BTP strategy.

 Takeaways

• BTP (Business Technology Platform) has multiple runtime options: Kyma, Cloud Foundry and ABAP.
• Kyma is based on Kubernetes and operates on-demand, starting and stopping when required.
• Business Application Studio is a good example for a Kyma case. It is maybe not running on Kyma but uses the same concept under the hood, Kubernetes pods. With this, BAS doesn’t need to run all the time and only requires resource when it is started. That’s also the reason you need to start it every morning.
• Kyma's pay-per-use model might be a cost-effective option if your use case requires non-24/7 operations.
• Cloud Foundry is more suitable for applications that need to be operational 24/7, like Fiori applications.
• Cloud Foundry is generally a more affordable option for always-on applications, offering greater accessibility.
•  Cloud Foundry supports building applications using various development languages and/or frameworks, such as Java, NodeJS, GO and Python.
• Companies can choose to activate multiple runtimes or select one based on their specific needs.
• ABAP could be more expensive for single applications, but it might become cost-effective for large-scale application development.
•  Each company should assess its developer skill set and the number of applications to be built when deciding on the best runtime strategy for BTP.