Book Image

Serverless Design Patterns and Best Practices

By : Brian Zambrano
Book Image

Serverless Design Patterns and Best Practices

By: Brian Zambrano

Overview of this book

Serverless applications handle many problems that developers face when running systems and servers. The serverless pay-per-invocation model can also result in drastic cost savings, contributing to its popularity. While it's simple to create a basic serverless application, it's critical to structure your software correctly to ensure it continues to succeed as it grows. Serverless Design Patterns and Best Practices presents patterns that can be adapted to run in a serverless environment. You will learn how to develop applications that are scalable, fault tolerant, and well-tested. The book begins with an introduction to the different design pattern categories available for serverless applications. You will learn thetrade-offs between GraphQL and REST and how they fare regarding overall application design in a serverless ecosystem. The book will also show you how to migrate an existing API to a serverless backend using AWS API Gateway. You will learn how to build event-driven applications using queuing and streaming systems, such as AWS Simple Queuing Service (SQS) and AWS Kinesis. Patterns for data-intensive serverless application are also explained, including the lambda architecture and MapReduce. This book will equip you with the knowledge and skills you need to develop scalable and resilient serverless applications confidently.
Table of Contents (18 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Iteration and deployment


Inevitably, there will be multiple deployments when developing an application such as this, and even once the first production version has shipped. Serverless speeds up this process dramatically, and once you experience the increased velocity, you may have a hard time going back to your old ways.

A deployment with the Serverless Framework consists of one command with a couple of variations.

Deploying the entire stack

To deploy everything in the serverless.yml file, the deploy command is used, specifying the stage (-s) variable (which defaults to dev):

# serverless deploy -s $ENV

Note

The make deploy target in use for this chapter's example executes this exact command.

When doing a full deployment like this, Serverless will upload your Lambda resources and execute the entire CloudFormation template. Even with a simple CloudFormation template, this can take several seconds. With bigger stacks, it can be even longer. It's unfortunate that some people believe this is the only...