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

Setting up CD and deployments with CircleCI


As I mentioned in the introductory section of this chapter, the D in CD stands for Delivery. In this section, we'll walk through the details of setting up both delivery and deployment of our application via CircleCI. I will admit, the boundaries here between delivery and deployment are a bit blurred, and any such discussions can become difficult due to disagreements in terminology and details. For our purposes, our CD pipeline will focus on the following:

  • Visibility
  • Feedback
  • Ease of automated deployments

For visibility and feedback, we'll use Slack and GitHub badges. Our existing deployment script from the Makefile and the serverless framework will be hooked into CircleCI to make production deployments fast, simple, and reliable.

Setting up Slack notifications

CircleCI has several integrations with various chat systems. Setting up test results to be posted to Slack (or your messaging platform of choice) is a straightforward and effective way to disseminate...