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

Simple proxy to a legacy API


In this first example, we'll go through the steps to set up a simple integration with an existing API. What is neat about API Gateway is that it's possible to go a very long way on the path to replacing current application code without writing any code ourselves. 

Note

In these examples, we'll use a publicly available fake API called JsonPlaceholder, pretending for our purposes that it's a legacy API that we'd like to replace: https://jsonplaceholder.typicode.com.

Of course, this type of replacement warrants plenty of thought and careful planning. Authentication, rate limiting, DNS entries, and the like are all factors that much be thought through carefully before embarking on such a project. Still, with all of the issues that one should consider, there are many tools and options to make this pattern a real possibility for many applications.

Setting up a pass-through proxy

Step one on our journey will be to work through the steps of setting up a new API in API Gateway...