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)

Creating a .proto file definition

Since the goal of this chapter is to write a template that we can use for later projects, we are going to create a dummy proto file that will let us test whether our build system is working properly or not. This dummy proto file will contain both a message and a service because we want to test code generation for both Protobuf and gRPC.

The message, called DummyMessage, will be defined as follows:

message DummyMessage {}

The service, called DummyService, will be defined as follows:

service DummyService {}

Now, because we are planning to generate Golang code, we still need to define an option called go_package and set its value to the name of the Go module concatenated with the name of the subfolder containing the proto files. This option is important because it lets us define the package in which the generated code should be. In our case, the project architecture is the following:

├── client
│ &...