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

Specifying deadlines

Deadlines are the most important thing when we are dealing with asynchronous communication. This is because a call could never return due to network or other problems. That is why Google recommends that we set a deadline for each of our RPC calls. Fortunately for us, this is as easy as canceling a call.

The first thing that we need to do, on the client side, is to create a context. This is similar to the WithCancel function, but this time, we will use WithTimeout. It takes a parent context like WithCancel but on top of that, it takes a Time instance representing the maximum amount of time for which we are willing to wait for a server answer.

Instead of WithCancel in printTasks, we are now going to have the following context:

ctx, cancel := context.WithTimeout(context.Background(), 1*time.Millisecond)
defer cancel()

Obviously, a timeout of 1 millisecond is way too low to let the server answer, but this is done on purpose so that we can get a DeadlineExceeded...