Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Serverless Design Patterns and Best Practices
  • Toc
  • feedback
Serverless Design Patterns and Best Practices

Serverless Design Patterns and Best Practices

By : Zambrano
5 (1)
close
Serverless Design Patterns and Best Practices

Serverless Design Patterns and Best Practices

5 (1)
By: 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 (12 chapters)
close

Error tracking


Practically speaking, all software systems crash at some point. One of the reasons I love working with serverless systems so much is that they, by their very nature, keep an application relatively small and more akin to a microservice, rather than a broad monolithic application. This fact by itself can drastically reduce the number of ways an application can fail. However, at some point, it will fail, and an exception you didn't expect will occur. What, then, is the best way to handle unexpected exceptions in a serverless system?

The good news here is that we have multiple options, and that some systems you may already be familiar with can work in the same way as they would in a non-serverless system. In the following sections, we'll walk through the steps for integrating two popular error tracking services, Sentry and Rollbar. Both services offer similar functionality and are equally easy to set up. In the following examples, we'll be using Python, but both Sentry and Rollbar...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete