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)

Infrastructure as Code with CloudFormation

Starting from this section, we will learn how to use a very important AWS tool, CloudFormation. AWS resources mostly have complicated and countless options, and provisioning them manually using AWS Console is not always a good option because this manual process may cause an issue because of a misconfiguration or forgotten option; also, the provisioning process would not be reproducible. Assume that you have to migrate the whole application to another AWS account or you want to remove and create everything from scratch. Creating BASH scripts with AWS CLI commands might be another option, but it would not solve some of the problems mentioned earlier; for example, deleting the whole application or changing some of the configuration in our stack would need refactoring of the BASH script or finding and removing the resources belonging to your...