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

Chapter 5. Scaling Out with the Fan-Out Pattern

The next turn in our serverless journey takes us away from web-centric patterns and towards those suitable for a variety of problems, web and otherwise. In this chapter, we'll discuss the fan-out pattern, which may be used in many different contexts, either by itself as a standalone system or within a larger project as a sub-unit. Conceptually, the fan-out pattern is precisely what it sounds like—one serverless entry point results in multiple invocations of downstream systems. Big data platforms and computer science algorithms have been using this trick for a very long time; by taking a sizable computational problem and breaking it into smaller pieces, a system can get to the result faster by working on those smaller pieces concurrently. Conceptually, this is precisely how MapReduce works in the mapping step. 

In this chapter, we will discuss how to split a single unit of work into multiple smaller groups of work using the fan-out pattern. We...