SAP Kyma Runtime (SKR) for Partners
In this regard, the SAP managed kubernetes cluster – SKR – offers an unprecedented opportunity to mix and match partners bespoke technology platforms and solutions with SAP’s BTP selection of runtimes and a treasure trove of services.
Let’s see how this story unfolds based on selected use cases…
Good to know:
Selected use cases.
Using Kyma functions for micro-services development alongside with other BTP services and runtimes.
Kyma brings the support of functions that allow for fast-tracked development of micro-services without the need of having to explicitly create containers.
Moreover the functions are server-less meaning they are lightweight and asynchronously executed by a managed Express (for nodejs functions) or Python based server. For instance:
You can also use functions to create your own APIs and then use SAP API Management to expose them to business users for consumption with LCNC productivity tools of the likes of Appgyver or Mendix….
Using Kyma to host and orchestrate containerised application workloads.
|A growing number of software solutions are provided as containers. One can easily find container libraries that offer ready to deploy k8s workloads, for instance:
Likewise, you could have created a library of containers for your own bespoke workloads, for instance:
Just think of k8s as of a cloud native operating systems where all you need to do is to yaml–describe how you want it to run your application workloads.
Additionally, with SKR you get access to a catalog of SAP BTP native services with the likes of XSUAA, Connectivity Proxy and Destination services…
(And the list of catalog services that can be natively consumed from Kyma side is ever growing.)
Regardless, any SAP BTP or foreign service can be consumed on Kyma side via service keys access mechanism (or its equivalent).
Last but not least, you can also bring your own services to the catalog…