Skip to main content

Is gRPC Overhyped?


gRPC has emerged as a popular choice for building modern APIs, but confusion often surrounds its inner workings and when it truly shines. This article aims to clarify the protocol underlying gRPC, its communication flow, and when REST APIs might be a better fit.

The Foundation: HTTP/2 Takes the Stage

Contrary to popular belief, gRPC itself is not a protocol. It leverages the HTTP/2 protocol as its transport layer, offering several advantages over traditional HTTP/1.1:

  • Multiplexing: Enables sending and receiving multiple requests and responses concurrently over a single connection, improving performance and reducing latency.
  • Header Compression: Reduces overhead by compressing request and response headers, further enhancing efficiency.
  • Server Push: Allows servers to proactively send additional resources (e.g., images, stylesheets) anticipated by the client, improving perceived performance.

gRPC in Action

gRPC builds upon HTTP/2 by defining a structured way to exchange data:

  1. Service Definition: Developers define service interfaces using a language-agnostic specification called Protocol Buffers (protobuf). This defines the data structures and methods (remote procedure calls) exposed by the service.


Protocol Buffers
// Define a service for getting user information
service UserService {
  rpc GetUser(GetuserRequest) returns (User)

// Define the request message
message GetuserRequest {
  string user_id = 1;

// Define the response message
message User {
  string name = 1;
  int32 age = 2;
  1. Client-Server Communication:
    • Clients:
      • Marshall data into protobuf messages based on the service definition.
      • Send these messages along with relevant metadata through HTTP/2 requests.

Example (Python client):

# Import necessary libraries
import grpc

# Define the request message
request = user_pb2.GetUserRequest(user_id="123")

# Connect to the server
channel = grpc.insecure_channel('localhost:50051')
stub = user_pb2_grpc.UserServiceStub(channel)

# Send the request and receive the response
response = stub.GetUser(request)

# Print the user information
print(f"Name: {}, Age: {response.age}")
* **Servers:**
    * Receive requests and extract data using protobuf.
    * Process the request and generate a response.
    * Marshall the response data into a protobuf message.
    * Send the response message and metadata back to the client.

What You Don't See

Unlike REST APIs, where you directly interact with raw HTTP requests and responses, gRPC hides the underlying byte streams exchanged between client and server. This abstraction offers several benefits:

  • Language Agnostic: Protobuf messages are language-independent, enabling seamless communication between clients and servers written in different languages.
  • Improved Developer Experience: Developers focus on defining service logic and data structures, leaving the low-level communication details to gRPC.
  • Error Handling: gRPC handles error codes and messages gracefully, simplifying error handling for developers.

However, this abstraction comes with a trade-off:

  • Limited Visibility: You cannot directly inspect the raw bytes being exchanged, making debugging certain issues more challenging. Imagine trying to understand a conversation happening in a foreign language without any subtitles or translation. While gRPC provides some debugging tools, analyzing the actual byte flow on the network can be complex and require specialized knowledge.

gRPC Bytes:

A simplified illustration:

Client sends a GetUser request with user_id="123":

(Binary data representing the following information)
- HTTP/2 frame type: HEADERS
- gRPC specific headers (e.g., method name, service name)
- Protobuf encoded message containing user_id="123"

Server sends a response with user information:

(Binary data representing the following information)
- HTTP/2 frame type: HEADERS
- gRPC specific headers (e.g., status code)
- Protobuf encoded message containing name="John Doe", age=30

REST vs. gRPC: Choosing the Right Tool for the Job

While gRPC offers performance benefits and streamlined development, it's not a one-size in many cases you can just stick with REST.


Popular posts from this blog

Functional Programming in Scala for Working Class OOP Java Programmers - Part 1

Introduction Have you ever been to a scala conf and told yourself "I have no idea what this guy talks about?" did you look nervously around and see all people smiling saying "yeah that's obvious " only to get you even more nervous? . If so this post is for you, otherwise just skip it, you already know fp in scala ;) This post is optimistic, although I'm going to say functional programming in scala is not easy, our target is to understand it, so bare with me. Let's face the truth functional programmin in scala is difficult if is difficult if you are just another working class programmer coming mainly from java background. If you came from haskell background then hell it's easy. If you come from heavy math background then hell yes it's easy. But if you are a standard working class java backend engineer with previous OOP design background then hell yeah it's difficult. Scala and Design Patterns An interesting point of view on scala, is

Alternatives to Using UUIDs

  Alternatives to Using UUIDs UUIDs are valuable for several reasons: Global Uniqueness : UUIDs are designed to be globally unique across systems, ensuring that no two identifiers collide unintentionally. This property is crucial for distributed systems, databases, and scenarios where data needs to be uniquely identified regardless of location or time. Standardization : UUIDs adhere to well-defined formats (such as UUIDv4) and are widely supported by various programming languages and platforms. This consistency simplifies interoperability and data exchange. High Collision Resistance : The probability of generating duplicate UUIDs is extremely low due to the combination of timestamp, random bits, and other factors. This collision resistance is essential for avoiding data corruption. However, there are situations where UUIDs may not be the optimal choice: Length and Readability : UUIDs are lengthy (typically 36 characters in their canonical form) and may not be human-readable. In URLs,

Dev OnCall Patterns

Introduction Being On-Call is not easy. So does writing software. Being On-Call is not just a magic solution, anyone who has been On-Call can tell you that, it's a stressful, you could be woken up at the middle of the night, and be undress stress, there are way's to mitigate that. White having software developers as On-Calls has its benefits, in order to preserve the benefits you should take special measurements in order to mitigate the stress and lack of sleep missing work-life balance that comes along with it. Many software developers can tell you that even if they were not being contacted the thought of being available 24/7 had its toll on them. But on the contrary a software developer who is an On-Call's gains many insights into troubleshooting, responsibility and deeper understanding of the code that he and his peers wrote. Being an On-Call all has become a natural part of software development. Please note I do not call software development software engineering b