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

Presentation layer


In  Chapter 2, A Three-Tier Web Application using REST, our React application was making API calls to our REST endpoints. This REST API that we built returns JSON, which our frontend code easily digests and feeds into our React code for rendering UI elements.

With a change to a GraphQL-based API, our frontend code will need to change somewhat drastically for the data-fetching sections. GraphQL behaves very differently than REST, and there is no corollary between a REST endpoint, which returns a known set of data, and GraphQL. Each GraphQL query is unique in that the client is responsible for asking for a specific set of data.

We won't review the changes to the frontend code. At the time of writing, popular choices for GraphQL for the frontend are Apollo and Relay. Apollo comes out of the Meteor Development Group and Facebook is behind Relay. Both are open source and popular in the GraphQL community. There are many resources on both topics all over the internet and readers...