Book Image

gRPC Go for Professionals

By : Clément Jean
Book Image

gRPC Go for Professionals

By: Clément Jean

Overview of this book

In recent years, the popularity of microservice architecture has surged, bringing forth a new set of requirements. Among these, efficient communication between the different services takes center stage, and that's where gRPC shines. This book will take you through creating gRPC servers and clients in an efficient, secure, and scalable way. However, communication is just one aspect of microservices, so this book goes beyond that to show you how to deploy your application on Kubernetes and configure other tools that are needed for making your application more resilient. With these tools at your disposal, you’ll be ready to get started with using gRPC in a microservice architecture. In gRPC Go for Professionals, you'll explore core concepts such as message transmission and the role of Protobuf in serialization and deserialization. Through a step-by-step implementation of a TODO list API, you’ll see the different features of gRPC in action. You’ll then learn different approaches for testing your services and debugging your API endpoints. Finally, you’ll get to grips with deploying the application services via Docker images and Kubernetes.
Table of Contents (13 chapters)
10
Epilogue

Technical requirements

For this chapter, you will find the relevant code in the folder called chapter7 in the accompanying GitHub repository (https://github.com/PacktPublishing/gRPC-Go-for-Professionals/tree/main/chapter7).

In the last section, I will use Kubernetes to show client-side load balancing. I assume that you already have Docker installed and a Kubernetes cluster. This can be done any way you want, but I provide a Kind (https://kind.sigs.k8s.io/) configuration to spin up a cluster easily and locally. This configuration is situated under the k8s folder of chapter7 and in the file called kind.yaml. Once Kind is installed, you can use it like so:

$ kind create cluster --config k8s/kind.yaml

And you can dispose of it by running the following command:

$ kind delete cluster