Book Image

Serverless Architectures with Kubernetes

By : Onur Yılmaz, Sathsara Sarathchandra
Book Image

Serverless Architectures with Kubernetes

By: Onur Yılmaz, Sathsara Sarathchandra

Overview of this book

Kubernetes has established itself as the standard platform for container management, orchestration, and deployment. By learning Kubernetes, you’ll be able to design your own serverless architecture by implementing the function-as-a-service (FaaS) model. After an accelerated, hands-on overview of the serverless architecture and various Kubernetes concepts, you’ll cover a wide range of real-world development challenges faced by real-world developers, and explore various techniques to overcome them. You’ll learn how to create production-ready Kubernetes clusters and run serverless applications on them. You'll see how Kubernetes platforms and serverless frameworks such as Kubeless, Apache OpenWhisk and OpenFaaS provide the tooling to help you develop serverless applications on Kubernetes. You'll also learn ways to select the appropriate framework for your upcoming project. By the end of this book, you’ll have the skills and confidence to design your own serverless applications using the power and flexibility of Kubernetes.
Table of Contents (11 chapters)
2
2. Introduction to Serverless in the Cloud

OpenWhisk Feeds, Triggers, and Rules

In the previous sections, we learned how to invoke actions either with the wsk CLI or with HTTP requests using web actions. In this section, we are going to learn how to automate action invocation with OpenWhisk feeds, triggers, and rules. The following diagram illustrates how actions are invoked with events from external event sources using feeds, triggers, and rules:

Figure 8.53: OpenWhisk Feeds, triggers, and rules

Triggers are different types of events sent from event sources. These triggers can be fired either manually with the wsk CLI or automatically from events occurring in external event sources. Some examples of an event source are a Git repository, an email account, or a Slack channel. As illustrated in the preceding diagram, feeds are used to connect the triggers to external event sources. Examples for feeds are as follows:

  • A commit is made to a Git repository.
  • Incoming email messages to a particular...