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

Summary

In this chapter, we saw the key features that we get out of the box when using gRPC. We saw that we return errors with error codes and messages. There are way fewer error codes in gRPC than in HTTP, which makes them less ambiguous.

After that, we saw that we can use the context to make a call cancelable and specify deadlines. These features are important for making reliable calls and making sure that if something goes wrong on the server side before returning, our client is not waiting indefinitely.

With context and interceptors, we also saw that we can send metadata and use them to validate requests. In our case, we checked for an authentication token every time a request was made. On the client side, we saw that interceptors can automatically add the metadata for us. This is especially useful for metadata that is shared across services and/or endpoints.

Then, we saw how we can encrypt communication over the network. We used TLS, as this is the most common way to...