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

The server streaming API

Important note

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

Now, that we know how to register a service, interact with a “database,” and run our client and server, everything will be faster. We will focus mostly on the API endpoint itself. In our case, we are going to create a ListTasks endpoint, which, as its name suggests, lists all the available tasks in the database.

One thing that we are going to do to make this a little bit fancier is that for each task listed, we are going to return whether this task is overdue or not. This is mostly done so that you can see how to provide more information about a certain object in the response object.

So, in the todo.proto file, we are going to add an RPC endpoint called ListTasks, which will take ListTasksRequest and return a stream...