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

Deployment


With a new Lambda function comes the need to deploy our code, which requires a full deployment via sls deploy. As a reminder, any time you add, remove, or otherwise update an AWS resource, a complete CloudFormation update is needed. We need to add a couple of new entries in the serverless.yml file, which will call the new graphql handler functions:

    functions:
     GraphQL:
       handler: handler.graphql
       events:
         - http:
             path: graphql
             method: get
             cors: true
         - http:
             path: graphql
             method: post
             cors: true

GraphQL will accept both GET and POST requests, so we'll wire methods to the same /graphql endpoint and make sure we enable CORS.

Since we're using new libraries, Graphene and Graphene-SQLAlchemy, we'll need to update our requirements file and rebuild our supporting libraries. I've added the following library to a specific commit to the requirements.txt file:

git+https://github...