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 read/write flow

Now that we have seen what Protobuf and gRPC are, it is time to go back to the read/write flow that we presented in Chapter 1. The goal of doing this is to make it a little bit more detailed and include what we learned.

As a quick reminder, we saw that they are mostly three levels when writing and reading data. We have the user code, the gRPC framework, and the transport layers. What is interesting for us here is mostly the user code. We did not go into too much detail in Chapter 1 but now that we are equipped with more knowledge on what gRPC is doing, we can understand the process more clearly.

The user-code layer is the code that developers write and interacts with the gRPC framework. For the client, this is calling the endpoints, and for the server, this is the implementation of the endpoints. If we keep going with our AccountService service, we can give a concrete example of the read/write flow.

The first thing that we can do is separate the user-code...