Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Serverless Architectures with Kubernetes

You're reading from   Serverless Architectures with Kubernetes Create production-ready Kubernetes clusters and run serverless applications on them

Arrow left icon
Product type Paperback
Published in Nov 2019
Publisher
ISBN-13 9781838983277
Length 474 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Onur Yılmaz Onur Yılmaz
Author Profile Icon Onur Yılmaz
Onur Yılmaz
Sathsara Sarathchandra Sathsara Sarathchandra
Author Profile Icon Sathsara Sarathchandra
Sathsara Sarathchandra
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Introduction to Serverless FREE CHAPTER 2. Introduction to Serverless in the Cloud 3. Introduction to Serverless Frameworks 4. Kubernetes Deep Dive 5. Production-Ready Kubernetes Clusters 6. Upcoming Serverless Features in Kubernetes 7. Kubernetes Serverless with Kubeless 8. Introduction to Apache OpenWhisk 9. Going Serverless with OpenFaaS Appendix

OpenWhisk Actions

In OpenWhisk, actions are code snippets written by developers that will be executed in response to events. These actions can be written in any programming language supported by OpenWhisk:

  • Ballerina
  • Go
  • Java
  • JavaScript
  • PHP
  • Python
  • Ruby
  • Swift
  • .NET Core

Also, we can use a custom Docker image if our preferred language runtime is not supported by OpenWhisk yet. These actions will receive a JSON object as input, then perform the necessary processing within the action, and finally return a JSON object with the processed results. In the following sections, we will focus on how to write, create, list, invoke, update, and delete OpenWhisk actions using the wsk CLI.

Writing Actions for OpenWhisk

When writing OpenWhisk actions with your preferred language, there are few standards that you must follow. They are as follows:

  • Each action should have a function named main, which is the entry point of the action. The source...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime