Book Image

Building Distributed Applications in Gin

By : Mohamed Labouardy
4 (1)
Book Image

Building Distributed Applications in Gin

4 (1)
By: Mohamed Labouardy

Overview of this book

Gin is a high-performance HTTP web framework used to build web applications and microservices in Go. This book is designed to teach you the ins and outs of the Gin framework with the help of practical examples. You’ll start by exploring the basics of the Gin framework, before progressing to build a real-world RESTful API. Along the way, you’ll learn how to write custom middleware and understand the routing mechanism, as well as how to bind user data and validate incoming HTTP requests. The book also demonstrates how to store and retrieve data at scale with a NoSQL database such as MongoDB, and how to implement a caching layer with Redis. Next, you’ll understand how to secure and test your API endpoints with authentication protocols such as OAuth 2 and JWT. Later chapters will guide you through rendering HTML templates on the server-side and building a frontend application with the React web framework to consume API responses. Finally, you’ll deploy your application on Amazon Web Services (AWS) and learn how to automate the deployment process with a continuous integration and continuous delivery (CI/CD) pipeline. By the end of this Gin book, you will be able to design, build, and deploy a production-ready distributed application from scratch using the Gin framework.
Table of Contents (16 chapters)
1
Section 1: Inside the Gin Framework
3
Section 2: Distributed Microservices
9
Section 3: Beyond the Basics

Summary

In this chapter, we learned how to build a RESTful API that leverages the Gin framework and Go driver for creating queries and querying in a NoSQL database such as MongoDB.

We also explored how to speed up the API by caching the data it accesses with Redis. It is definitely a great addition to your application if your data is mostly static and does not change constantly. Finally, we covered how to run performance benchmarks with Apache Benchmark.

The RESTful API we have built so far works like a charm and is open to the public (if deployed on a remote server). If you leave the API unauthenticated, then anybody can hit any endpoint, which may very undesirable as your data could be damaged by users. Even worse, you might expose sensitive information from your database to the whole internet. That's why, in the next chapter, we will cover how to secure the API with authentication, such as JWT.