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)

The bidirectional streaming API

Important note

In terms of the underlying protocol, the bidirectional streaming API uses Send Header from the client side, followed by multiple Send Message from the server and/or client side, Half-Close from the client side, and finally Send Trailer from the server side.

In a bidirectional streaming API, the goal is to let the client send zero or more requests and let the server send zero or more responses. We are going to use this to simulate a feature that is like updateTasks but in which we are going to have direct feedback from the DeleteTasks endpoint API after each deletion instead of waiting for all the deletions to be done.

One thing to be clear about before continuing with the implementation is the question of why not to design DeleteTasks as a server streaming API or updateTasks as a bidirectional streaming API. The difference between these two tasks is how “destructive” they are. We can make an update directly on the...