Book Image

Building Serverless Architectures

By : Cagatay Gurturk
Book Image

Building Serverless Architectures

By: Cagatay Gurturk

Overview of this book

Over the past years, all kind of companies from start-ups to giant enterprises started their move to public cloud providers in order to save their costs and reduce the operation effort needed to keep their shops open. Now it is even possible to craft a complex software system consisting of many independent micro-functions that will run only when they are needed without needing to maintain individual servers. The focus of this book is to design serverless architectures, and weigh the advantages and disadvantages of this approach, along with decision factors to consider. You will learn how to design a serverless application, get to know that key points of services that serverless applications are based on, and known issues and solutions. The book addresses key challenges such as how to slice out the core functionality of the software to be distributed in different cloud services and cloud functions. It covers basic and advanced usage of these services, testing and securing the serverless software, automating deployment, and more. By the end of the book, you will be equipped with knowledge of new tools and techniques to keep up with this evolution in the IT industry.
Table of Contents (10 chapters)

Creating CloudWatch metrics from application logs

As we've seen before, Lambda functions save their log events to CloudWatch. This lets us to watch our application's status easily, and we do not have to maintain any logging infrastructure for that. This is already a cool feature.

If you've ever used a logging solution such as Kibana, you should be familiar with saving search patterns in it, so you can create graphs using the occurrence frequency of a pattern in your logs. This is possible to have some functionality very easily in CloudWatch logs. This feature is called Create Metric Filter and automatically tests custom patterns against log lines and pushes them as a metric to CloudWatch. With that, for example, you can see how many times your log contained an ERROR string, you can monitor it via CloudWatch graphics, or you can even create alarms and take action...