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

Logic layer


GraphQL simplifies life for clients because there is a single HTTP endpoint. In some ways, this makes the pattern for a serverless GraphQL API extremely simple and in some ways quite dull.

If we were starting this GraphQL web application from scratch, there would be plenty of decisions to make and material to cover to make our application code modular, easy to test, and well designed. Since we're porting the example REST web application, we have already implemented the vast majority of the needed functionality and software layers. These sections may seem terser than expected, especially if you have skipped Chapter 2, A Three-Tier Web Application using REST. Any gaps in code organization or layout, configuration strategy, deployments, and so on can be filled by reviewing Chapter 2, Three-Tier Web Application using REST.

Organization of the Lambda functions

REST APIs are built around resources that each own their own URI, in part to give clients a well-known or predictable way to...