@ -5,9 +5,6 @@ description: "Learn how to deploy your first AWS Lambda serverless function usin
slug: "creating-serverless-lambda-go"
isPublish: true
---
Creating Serverless Applications with AWS Lambda and Go
---
In recent years, serverless computing has become a popular choice for building scalable, flexible, and cost-effective applications. Using serverless solutions, you can focus on writing and deploying code, without having to worry about managing infrastructure. AWS Lambda, Amazon's serverless computing platform, provides a simple and efficient way to run code in response to events, without having to provision or manage servers. In this blog post, I'll take a look at how to build serverless applications using AWS Lambda and the Go programming language. I'll cover the basics of serverless computing, setting up an AWS Lambda function, and writing Go code to handle events and respond to requests. By the end of this post, you'll have a good understanding of how to build and deploy serverless applications using AWS Lambda and Go. Let's get started.
Building a Stateless, Containerized Trivia API in Golang
---
While working on a much larger project, I decided it would be a good idea to make something smaller that could show off how much I have improved my development strategies and back end knowledge since the days of my first full stack project, Massflip. Today, I will be walking you through my process of creating a trivia API that will allow people to get random trivia questions and then check their answers for correctness. Since this is supposed to be a stateless system, there should be no writing to a database when getting trivia questions or verifying answers. In fact, we won't have any database at all, other than however we choose to store our trivia questions (for this project, our questions will be stored in a json file that gets loaded into memory, but you could modify it to use an SQL database or similar).
Now since I don't really know anything about trivia terminology, let's go over the terms I have decided to use when referring to our objects.
Running `go test ./...` now will show us just how many errors can go unnoticed without proper error handling and enforcement of fail behavior in our API.