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

Introduction to CI/CD


CI and CD are often grouped in discussions around software development life cycles or software engineering best practices. However, CI and CD are distinct concepts with their own sets of best practices, challenges, and goals. This section will not attempt to cover the broad subject of CI and CD, but it is essential to talk about a few concepts and ideas to have a discussion that applies to serverless architectures and systems.

Most of these ideas were born out of the Agile and Extreme Programming (XP) communities. While these are not hard rules that every team needs to follow, they do come from groups of people who were looking to solve real-world problems. Adopting these practices can help any team and any project, whether the project is serverless or not.

CI

CI is the process of merging code changes into a mainline branch (for example, often a master branch if using Git) early and often. Before a merge from a development branch to a master branch, some preconditions...