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

Compressing the payload

While Protobuf serializes data into binary and this involves much smaller payloads than text data, we can apply compression on top of the binary. gRPC provides us with the gzip Compressor (https://pkg.go.dev/google.golang.org/grpc/encoding/gzip) and for more advanced use cases, lets us write our own Compressor (https://pkg.go.dev/google.golang.org/grpc/encoding).

Now, before diving into how to use the gzip Compressor, it is important to understand that lossless compression might result in a bigger payload size. If your payload does not contain repetitive data, which is what gzip detects and compresses, you will send more bytes than needed. So, you will need to experiment with a typical payload and see how gzip affects its size.

To show an example of that, I included in the helpers folder a file called gzip.go, which contains a helper function called compressedSize. This function returns the original size of the serialized data and its size after gzip compression...