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

Server and Dial options

We touched upon ServerOption and DialOption briefly with the grpc.ServerOption object and the grpc.WithTransportCredentials function. However, there are a lot of other options you can choose from. For readability’s sake, I will not go into detail about every one of them, but I want to present some major options that you will probably use. All ServerOptions can be found at the root of the grpc-go repository in the file called server.go (https://github.com/grpc/grpc-go/blob/master/server.go) and the DialOptions in the file called dialoptions.go (https://github.com/grpc/grpc-go/blob/master/dialoptions.go).

grpc.Creds

This is an option, on both the server and client sides, that we will use when we talk about securing APIs. For now, we saw that we can call grpc.WithTransportCredentials with an insecure.NewCredentials result, and this gives us an insecure connection. This means that none of the requests and responses are encrypted; anyone could intercept...