Book Image

Serverless Programming Cookbook

By : Heartin Kanikathottu
Book Image

Serverless Programming Cookbook

By: Heartin Kanikathottu

Overview of this book

Managing physical servers will be a thing of the past once you’re able to harness the power of serverless computing. If you’re already prepped with the basics of serverless computing, Serverless Programming Cookbook will help you take the next step ahead. This recipe-based guide provides solutions to problems you might face while building serverless applications. You'll begin by setting up Amazon Web Services (AWS), the primary cloud provider used for most recipes. The next set of recipes will cover various components to build a Serverless application including REST APIs, database, user management, authentication, web hosting, domain registration, DNS management, CDN, messaging, notifications and monitoring. The book also introduces you to the latest technology trends such as Data Streams, Machine Learning and NLP. You will also see patterns and practices for using various services in a real world application. Finally, to broaden your understanding of Serverless computing, you'll also cover getting started guides for other cloud providers such as Azure, Google Cloud Platform and IBM cloud. By the end of this book, you’ll have acquired the skills you need to build serverless applications efficiently using various cloud offerings.
Table of Contents (12 chapters)

Introduction

In the previous chapters, you saw how to create Serverless functions, add REST APIs, create data stores, and secure an application. In this chapter, we will look at recipes related to hosting a website, such as how to register domain names, host a static website, attach the custom domain for our S3 bucket, and use the CloudFront Content Delivery Network (CDN). You already saw S3 in previous recipes. Amazon Route 53 is a new service that we will introduce in this chapter. The Route 53 service is Amazon's DNS management service for registering domains and implementing routing strategies.

Some Route 53 functionalities may be one-time activities (for example, domain registration), some may require user interaction at various stages (for example, domain ownership validation), and some may take a longer time to complete. For example, DNS propagation can take up to...