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

Why does gRPC matter?

Now that we have a sense of what gRPC is, we can get into why it matters. To explain gRPC’s role, we are going to compare it with two other ways of performing client/server communication. The first one is the traditional REST API architecture based on HTTP and JSON, and the second one is GraphQL.

REST

While I am assuming that most of you reading this book are familiar with REST APIs, I still believe that it is important to introduce the principles of designing such APIs. It will help us understand in which ways gRPC is like REST and in which it differs.

A REST API, as with every other technology in this comparison study, is an interface between an information provider and a consumer. When writing such an API, we expose endpoints on specific URLs (routes) that can be used by a client to create, read, update, and delete resource(s).

However, REST APIs are different from gRPC and GraphQL. The main difference is that REST is not a framework—...