Book Image

Docker for Serverless Applications

By : Chanwit Kaewkasi
Book Image

Docker for Serverless Applications

By: Chanwit Kaewkasi

Overview of this book

Serverless applications have gained a lot of popularity among developers and are currently the buzzwords in the tech market. Docker and serverless are two terms that go hand-in-hand. This book will start by explaining serverless and Function-as-a-Service (FaaS) concepts, and why they are important. Then, it will introduce the concepts of containerization and how Docker fits into the Serverless ideology. It will explore the architectures and components of three major Docker-based FaaS platforms, how to deploy and how to use their CLI. Then, this book will discuss how to set up and operate a production-grade Docker cluster. We will cover all concepts of FaaS frameworks with practical use cases, followed by deploying and orchestrating these serverless systems using Docker. Finally, we will also explore advanced topics and prototypes for FaaS architectures in the last chapter. By the end of this book, you will be in a position to build and deploy your own FaaS platform using Docker.
Table of Contents (15 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Beyond serverless


Hybrid serverless would be a deployment model that links hybrid cloud to the serverless deployment model. It is already started by IT vendors offering hardware rental services in the form of private clouds, putting them to customer's organizations, and charging at the rate of pay-as-you-go.

When the serverless and FaaS computing platforms are deployed on top of that kind of hybrid infrastructure, they become hybrid serverless. This could be the next generation of computing platform that allows you to store sensitive data inside the organization, having some important FaaS functions running on the local system, while leveraging some extra computing resources as pay-per-request. It will be in the scope of the definition of serverless, if the customer's organization does not need to maintain or administer any of the hardware servers. Fortunately, when mixing this model with what we have discussed throughout this book, using Docker as our infrastructure would still be applied...