Book Image

Hands-On Serverless Applications with Go

By : Mohamed Labouardy
Book Image

Hands-On Serverless Applications with Go

By: Mohamed Labouardy

Overview of this book

Serverless architecture is popular in the tech community due to AWS Lambda. Go is simple to learn, straightforward to work with, and easy to read for other developers; and now it's been heralded as a supported language for AWS Lambda. This book is your optimal guide to designing a Go serverless application and deploying it to Lambda. This book starts with a quick introduction to the world of serverless architecture and its benefits, and then delves into AWS Lambda using practical examples. You'll then learn how to design and build a production-ready application in Go using AWS serverless services with zero upfront infrastructure investment. The book will help you learn how to scale up serverless applications and handle distributed serverless systems in production. You will also learn how to log and test your application. Along the way, you'll also discover how to set up a CI/CD pipeline to automate the deployment process of your Lambda functions. Moreover, you'll learn how to troubleshoot and monitor your apps in near real-time with services such as AWS CloudWatch and X-ray. This book will also teach you how to secure the access with AWS Cognito. By the end of this book, you will have mastered designing, building, and deploying a Go serverless application.
Table of Contents (17 chapters)

Unit testing

Unit testing your Lambda function means testing the function handler in total isolation (as far as possible) from external resources (such as the following events: DynamoDB, S3, Kinesis). These tests allow you to catch bugs before actually deploying your new changes to production and maintain the quality, reliability, and security of your source code.

Before we write our first unit test, some background about testing in Golang might be helpful. To write a new test suite in Go, the filename must end with _test.go and contain the functions with a TestFUNCTIONNAME prefix. The Test prefix helps to identify the test routine. The files that end with the _test suffix will be excluded while building the deployment package and will be executed only if the go test command is issued. In addition, Go comes with a built-in testing package with a lot of helper functions. However...