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

Caching an API with Redis

In this section, we will cover how to add a caching mechanism to our API. Let's imagine that we have a tremendous number of recipes in our MongoDB database. Every time we try to query a list of recipes, we struggle with performance issues. What we can do instead is use an in-memory database, such as Redis, to reuse previously retrieved recipes and avoiding hitting the MongoDB database on each request.

Redis is consistently faster at retrieving data because it is always in RAM – that's why it's an excellent choice for caching. On the other hand, MongoDB might have to retrieve data from disk for advancing queries.

According to the official documentation (https://redis.io/), Redis is an open source, distributed, in-memory, key-value database, cache, and message broker. The following diagram illustrates how Redis fits in our API architecture:

Figure 3.23 – API new architecture

Let's say we want to...