Kyma Kyma Capabilities Demos, 25 Aug 2019

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Hello World 3 Ways: 3b Kyma Lambdas

Description

I am a big fan of Thomas Jungs series about project Kyma and Kubernetes. In his last video √
Hello World 3 Ways: ABAP, Cloud Foundry, and Kubernetes (https://www.youtube.com/watch?v=lbJ2I964pfY) he compared on a simple scenario (the beloved HelloWorld webservice) ABAP, Cloud Foundry and Kyma/Kubernetes.
The conclusion was that going from ABAP to Cloud Foundry to Kyma/Kubernetes the platforms are getting less opinionated and therefore you get more flexibility but also have to solve more topics on your own and make decisions how to solve them. From the start of Kyma we also wanted to help to make simple things simple again by embracing serverless concepts and making simple things simple again.
To demonstrate this I simply use the Kyma Lambdas to implement Thomas Jungs HelloWorld example. And as you can in the demo this way you need a similar amount of lines of code / clicks to realize the HelloWorld example. And at the same time you are fully integrated in the cloud native environment Kyma provides. This allows you to use autoscaling, API & Event integration with the connected Applications and utilizing SAP & Hyperscaler services as needed with a few clicks or CLI calls.

Cheers,

Andreas

Note: I'm from the C/4CORE organisation inside SAP Customer experience. One of my teams main focus areas are the SAP Cloud Platform Extension Factory and the Opensource Project Kyma. So I think this makes me partially biased ;) Still this is not an "official" SAP product demo. I'm simply an enthusiastic developer using these tools and sharing my experiences.

If you are interested now you can find more information here:
* Kyma Website: https://kyma-project.io/
* Kyma Roadmap: https://kyma-project.io/roadmap/
* Kyma Youtube Channel: https://www.youtube.com/channel/UC8Q8bBtYe9gQN-dQ-_L8JvQ
* Official Enablement Material on the SAP Cloud Platform Extension Factory focusing on Kyma based use-cases: https://enable.cx.sap.com/tag/tagid/sap%20cloud%20platform%20extension%20factory

A

Hi, my name is andreas box. Take I'm working in the customer experience area of SRP and my team's and I are working different areas, but one of the main focus areas is extensibility and there we basically work on the s AP cloud platform, extension factory with our colleagues from the cloud platform and also on the open source project kima, which was also used by the extension factory, and I was very very happy with seeing Thomas Young's series about project kima and also kubernetes, and especially his last video around hello worlds.

A

We ways comparing the different platforms available from our Bob cloud, foundry to kubernetes, /, kima, I, think caught my attention, I liked it very much because it gave a good overview, especially if you're not familiar with the different or with each of these platforms. And so one of the conclusions in the end was that in kubernetes and kima.

A

So if there's a spectrum of opinionation- and it goes from above to cloud foundry to kubernetes and kima- and I think I agree that in kima you one of the strengths is that you can basically use all the power of the underlying stack and they're very useful and helpful frameworks around which can help you to create real cloud native extensions and applications and, as we also saw in some aspects like for the API exposure, kima is also taking an opinionated approach there, as we are curating a set of frameworks in kima, where we think it's very, very helpful for you in order to create a real cloud native application or extension, and so yes, so there you have a lot of lot of flexibility, but also in chemo.

A

We want to to ensure that we help to make simple things simple again, as we say, and therefore we from the get-go emphasized also serverless workloads and therefore especially for the given example, I think I wanted to also quickly show you how you can work. If you use the opinionated approach for service work clothes, how quickly, you can basically implement the example given by Thomas Young.

A

So therefore, I have a small vanilla cluster here, prepared and similar to Thomas I'm, going to create a namespace first leave all the settings in their default state and basically now I go instead of deploying or creating a lambda. Creating a container I will go directly to lambdas and click at lambda, so every lumber needs the name.

A

So we do this and then basically here we have the standard function body and in order just for the hello world example to return the text, we want to return. So we say here in a world and.

A

So now we would have the logic in this case now we need to ensure that it can be called via HTTP. So there are power, two possibilities here we have event triggers, which was basically so. The whole concept of kheema is that you can connect applications from SFP and there we work on default integrations, but also third-party applications on source projects, so that you can easily access their api s and also consume their events.

A

But in this case we trust' want to have an HTTP endpoint, and if you look at this screen, it looks a bit similar to what Thomas has shown in up up, because also here you have a way to enable authentication. But in our case we don't need this. So therefore you only get an HTTP endpoint here, where you can call your lambda later so I capitis already so having done this so now, all I have to do is click. Basically, here is a create button.

A

So what is happening in in the background? In the background, basically, all the things basically Thomas has shown before in order to deploy a service on Combinator schema like creating a first writing the program, then creating a docker container then scheduling these cantatas container on kubernetes.

A

This is all happening automatically in the background for you, bye, bye, kima, so and basically I see here the examples of hello world, it's already green, so it has already been deployed if I know the tap and click then I see here hello world, so that worked out fine I think in basically the same amount of code you had to write as in up up. We can even now do a change and safe again and now I'm a little bit quicker.

A

Then you see here there's a change, so one of two that basically means that kima in the background is catering, a rolling update. So for you and if I know XS here you see that already the changes are visible.

A

There are a lot of other aspects where the opinionation of akima comes into into the picture and where I can demonstrate a few other features, but that's basically all we had to do to cover the example on Thomas gave and I think that strengths here is that now you do this in a fully cloud native environment, and so you can basically, wherever you have more complicated requirements which doesn't fit the opinionation.

A

You can easily just utilize the underlying power of the technical stack, but even here you see we can decide with different templates we have given, but you can change them. How this lambda would basically scale up scale on do this or you can easily with service bindings, also excess services from NZ, connected application or from the hyper scalars directly in your lambda, so I think basically for Miki mer in this sense combines the two ends of the spectrum of opinionation right.

A

You have the full access of kubernetes and, in addition, you have this opinionated way which takes a lot of the decisions of your plate, because it's handled automatically for you and can basically result in very, very quick implementation times for certain yeah business problems you want to solve. Okay, I will also leave a few more further links if you're interested to our enablement material on enable dot, CX and other useful, useful links and yeah. If you have any questions, let me know so: thanks and Thomas keep up the good work.

A

I really enjoy your serious bye, bye.