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

Summary

In this chapter, we first learned about the history and the core concepts of Apache OpenWhisk. Then, we learned how to set up IBM Cloud Functions with CLI to run our serverless functions. After that, OpenWhisk actions were introduced, which are the code snippets written in one of the languages supported by OpenWhisk. We discussed how to write, create, list, invoke, update, and delete OpenWhisk actions using the wsk CLI. Next, we went over OpenWhisk sequences, which are used to combine multiple actions together to create a more complex processing pipeline. Going forward, we learned how to expose actions publicly using a URL with web actions. We discussed how web actions allow us to return additional information from the action, such as HTTP headers and non-JSON payloads, including HTML and binary data. The next section was on feeds, triggers, and rules that automate action invocation using events from external event sources. Finally, OpenWhisk packages were discussed, which...