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

System architecture


In many ways, this is the most straightforward pattern covered in this book. A single entry point, whether it be an HTTP request, some event notification, or anything else supported on your cloud provider of choice, triggers multiple invocations of some other serverless function in parallel. What one gains in this architecture is parallelism and hence speed. Our first example is one which is easy to understand and which you can view as the Hello World of serverless architectures.

Imagine a system which takes an image and creates multiple versions of the original image with different sizes smaller than the original. How can this be solved at its simplest? Once a user uploads an image, our system notices the new image upload and, using a for loop, iterates and creates the various thumbnails. Some fictitious code to do this may look like the following:

const sizes = [128, 256, 512, 1024];
const img = readSomeImage();

sizes.forEach(function(size) {
  img.resize(size, AUTO...