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

Handling errors

Up until now, we have not discussed potential errors that could appear within or outside of the business logic. This is obviously not great for a production-ready API, so we are going to see how to solve them. In this section, we are going to concentrate our efforts on the RPC endpoint called AddTask.

Before starting to code, we need to understand how errors work in gRPC, but this should not be hard because they are pretty similar to what we are used to in REST APIs.

Errors are returned with the help of a wrapper struct called Status. This struct can be built in multiple ways but the ones we are interested in this section are the following:

func Error(c codes.Code, msg string) error
func Errorf(c codes.Code, format string, a ...interface{}) error

They both take a message for the error and an error code. Let us focus on the codes since the messages are just strings describing the error. The status codes are predefined codes that are consistent across the...