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.

Related Content you might be interested in

Current Title:

Small book image
Building Serverless Architectures
Cagatay Gurturk
Jul, 2017 | 242 pages
Small book image
Serverless Programming Cookbook
Heartin Kanikathottu
Jan, 2019 | 490 pages
Small book image
Hands-On Serverless Applications with Kotlin
Hardik Trivedi | Ameya Kulkarni
Sep, 2018 | 386 pages
Small book image
Building Serverless Web Applications
Diego Zanon
Jul, 2017 | 354 pages
Table of Contents (10 chapters)
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
Getting Started with Serverless
Getting Started with Serverless
Preparing the environment
Gradle
Summary
Bibliography
2
Infrastructure as a Code
Infrastructure as a Code
Uploading the artifacts to Cloud
Infrastructure as Code with CloudFormation
Deploying our first Lambda with CloudFormation
Summary
3
Hello Internet
Hello Internet
Setting up API Gateway
Setting up the CloudFront CDN distribution
Summary
4
Applying Enterprise Patterns
Applying Enterprise Patterns
Creating User Service
Configuring Guice
Writing the Lambda Handler class with injected dependency
Adding logging
Service dependencies
Summary
5
Persisting Data
Persisting Data
Introduction to DynamoDB
Creating the first table
Summary
6
Building Supporting Services
Building Supporting Services
Writing the foundation of a Lambda function
Letting users upload to S3
Sending emails via SES
Consuming the SNS message and sending emails
Summary
7
Searching Data
Searching Data
Creating the search domain
Uploading test data
Creating the suggester
Creating the API endpoint for suggestions
Lambda function for updating search data
Summary
8
Monitoring, Logging, and Security
Monitoring, Logging, and Security
Setting up a Route53 health check
Wrapping everything up in CloudFormation
Creating CloudWatch metrics from application logs
Running Lambda functions in VPC
Summary
9
Lambda Framework
Lambda Framework
Getting to know Lambda Framework
Summary

Hello Internet

In previous chapters, we looked at how to build standalone, event-based Lambda functions. Lambda functions were code pieces living in the cloud that respond to different events, such as a new file in S3 bucket or an SNS notification, such as what we will see in following chapters. However, at this stage, maybe our simplest requirements would be to invoke the lambda function with an HTTP request, thus having a fully serverless REST API.

Thanks to API Gateway, it is possible to create a REST API that responds to HTTP requests. API Gateway replaces servlets, servlet containers, application servers, and basically the HTTP layer. When a request arrives at API Gateway, it decides where to route this request, transforms the input, invokes the "backend", and sends back the response to the client.

API Gateway can proxy to many types of backends, and it can be configured...

Previous Section
End of Section 1
Next Section