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)

Retrying calls

As of now, we have worked only on the server side. Let us now see an important feature on the client side. This feature is the retrying of calls that failed depending on the status code. This might be interesting for use cases where the network is unreliable. If we get an Unavailable error code, we will retry with an exponentially bigger wait time. This is because we do not want to retry too often and overload the network.

Important note

gRPC supports retries without the need for a third-party library. However, the configuration is quite verbose and not very well documented. If you are interested in trying it, you can check the following example:

Let us get the dependency that we need (client folder):

$ go get

Then, we can define some options for the retry. We will define how many times and on which...