 Hi, my name is Brian Tannis and I'm a developer advocate at Red Hat and I focus on OpenShift. But first off, what is Serverless? It's based on Knative. It's easy to install via an operator and I could deploy applications as a developer without needing to know Kubernetes YAML. It also allows us to scale by default with good defaults configured. We could scale down to zero to use some of our resources more effectively. And Serverless also enables event-driven application architecture. So we could have our application be triggered by an event that comes in via Kafka or an event bus or something that we build, maybe even camel K for example. So there are three different ways to deploy applications using Knative serving. And I want to show the differences between a deployment and a case service. We could see that we have some configuration, we've got a name, we have to specify some selectors and some labels, and we have to specify an image with some ports and some services as well as routes. You could see that that is our manifest to deploy this application using a traditional style deployment. So if we translate that into a Knative service, you could see there's a whole lot less YAML that we have to manage. So we could deploy our application using OC apply, and we could apply that deployment. We could also deploy the case service if we need to as well. So looking at the OpenShift developer console, we could see the two different deployments that we just used to deploy our app, the event display deployment, as well as the case service. So we could click on add and we could choose either from Git, so we could import source code from GitHub or GitLab or BitBucket for example. We could use container images, which is what we're going to use, or we could maybe even do a Docker file or something else. So to deploy the image, we need to specify which image to use, and we could see that's been validated. Next we could choose to deploy this using a standard Kubernetes style deployment or a Knative service. So we could specify the minimum number of pods. We could also maybe specify concurrency targets and limits so that we could scale up our application a little bit more quickly. The last way to deploy an application using Knative would be using the KNCLI. This also is a no yaml method. We just use switches to configure things and it's pretty easy to work with. We could update and create things and work with all the Knative tools. We could deploy the case service using the KNCLI tool really easily. So there are three different ways to tie an event source to a Knative service or a sync. One would be a simple direct connection. Another method would be using a channel in a subscription where a channel could have multiple sources and Knative services will subscribe to channels. So thirdly, we could use brokers and triggers to use the power of the event queue to filter notifications and events before they touch our Knative service. Within the OpenShift developer console, we could easily create an event source by dragging the arrow outside of the Knative service and choosing event source. And we could specify a Kafka source, but this could also be a camel k source or something that we created or anything else that passes events. And in here, we specify our source for Kafka as well as the topic and the group that we have. And there we go. With this, you'll see the Knative service is going to start ramping out because this event source already has quite a few events already flowing into it. So it's a busy event queue. We could see what's happening by clicking on one of the logs here and we could see that there are cloud events coming in. We could see different data and it's just an integer that's incrementing maybe a couple times each second. So with this, we've deployed an application using OpenShift serverless and we could see how easy it is to deploy that app and tie a Kafka event source to that application so that we could have an application that's built on event driven application architecture. If you're interested in trying out OpenShift, you could go to openshift.com slash try. If you're interested in learning a little bit more about OpenShift, check out learn.openshift.com. And lastly, if you're interested in learning more about Knative and OpenShift serverless, check out the Knative cookbook. It's available for free.