Skip to content
BENIBIX Learn

gRPC

Development🔌 APIsAPI Architecture Styles

Also known as gRPC API, Google RPC, gRPC-Web

A fast way for one service to call another. Its messages are small.

Think of it like

Think of it like sending notes in a secret shorthand. Both sides know the code, so notes are tiny and fast.

Example

Jack's 12 back-end services talk to each other with gRPC. One .proto file keeps every service's Go and Python code in step.

Why it matters

Its messages are smaller and faster than JSON. The shared file also catches wrong fields before the code runs.

Definition

gRPC is a fast way for services to call each other's functions. Google made it and opened it to everyone in 2015. You describe each service and its messages in a .proto file. Tools turn that file into ready code for many languages. Messages are sent in a small binary format called Protocol Buffers, over HTTP/2. It is fast and strict, so firms use it between their own services.

Common mistake

Using gRPC straight from a web page. Browsers need a helper layer, so public APIs usually stay REST.

Key takeaways

  1. 1
    A shared .proto file. Describes every call.
  2. 2
    Binary messages. Small and fast.
  3. 3
    Service to service. Its usual home.

Compare