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)

Using the template


This section is only necessary if you want to work with the same architecture as the github repository. Continuing working on the code from the previous code is totally fine.

If you remember, the goal of the previous chapter was to create a template that we can use to create a new gRPC project. As we will start such a project now, we will need to copy the content of the chapter4 folder into the chapter5 folder. To do that, simply run the following commands:

$ mkdir chapter5
$ cp -R chapter4/* chapter5

We pass –R in our case because we want to recursively copy all the files in the chapter4 folder.

And finally, we can also clean the template a little bit. We can remove the dummy directory in the proto folder because this was just there for testing our code generation. Then, if you used bazel for chapter4, we can delete all the build folders that start with the bazel- prefix. To do that, we can just simply remove them as follows:

$ cd chapter5...