Category gRPC

gRPC: synchronous and asynchronous Server streaming RPC

gRPC, one of the most popular RPC frameworks for inter-process microservices communication, supports both unary and streaming RPC. Contrary to unary RPC, in gRPC streaming RPC, a client sends a single request, and in return, the server sends a stream of messages. In this article, we will see how to implement server streaming RPC and how to handle errors in streaming response.

gRPC: synchronous and asynchronous unary RPC in Java

Photo by Ramón Salinero on Unsplash
gRPC, a remote procedure call (RPC) framework, is used for inter microservices communication. The gRPC supports both unary RPC and streaming RPC. In gRPC unary RPC, a client sends a single request and receives a single response. Additionally, an RPC in gRPC can be synchronous or asynchronous. In synchronous RPC, a client call waits for the server to respond. As the name suggests, in asynchronous RPC the server returns the response asynchronously.

gRPC for microservices communication

Microservices inter-process communication using gRPC
A microservices-based software system requires applications to talk to each other using an inter-process communication mechanism. gRPC is a modern inter-process communication system that is scalable and more efficient than the traditional RESTful services.

gRPC load balancing on Kubernetes (using Headless Service)

gRPC works on HTTP/2. The TCP connection on the HTP/2 is long-lived and a single connection can multiplex many requests. That means that connection-level load balancing is not very useful. The default load balancing in Kubernetes is based on connection level load balancing. This article is about how to implement load balancing using Kubernetes headless service.

Error handling in gRPC with public RESTFul API

Handling errors can be hard and it’s even harder if your application consists of many microservices exposing a mixture of REST and RPC APIs. The consumer of your API needs a consistent experience of error handling. In this article, we will see how to develop error handling, which works across RESTFul APIs and gRPC API.

Getting Error Handling right in gRPC

Photo by Markus Spiske on Unsplash
Getting errors right can be tricky and it can be even trickier in gRPC. The current version of gRPC only has limited built-in error handling based on simple status codes and metadata. In this article, we will see what are limitations of gRPC error handling and how to overcome that