What Is gRPC?

gRPC is a high-performance remote procedure call framework that lets a client call methods on a server as if they were local function calls, using Protocol B...

Published November 17, 2026

gRPC is a high-performance remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers, letting services call each other's methods as if they were local functions, with strongly typed generated clients.

The concept

You define services and messages in a .proto file; code generators create client and server stubs in many languages.

Protobuf is a compact binary format, and HTTP/2 enables multiplexing and streaming (unary, server, client and bidirectional). It is popular for microservice-to-microservice calls; browsers need gRPC-Web.

Contract first

callhandleClient stubgeneratedHTTP/2 + protobufbinaryServer implyour code
Both sides share the .proto contract.

Practical examples

user.proto

syntax = "proto3";
service Users { rpc GetUser (UserRequest) returns (User); }
message UserRequest { int32 id = 1; }
message User { int32 id = 1; string name = 2; }

Node client

client.GetUser({ id: 7 }, (err, user) => console.log(user.name))

Test from the shell

grpcurl -plaintext -d '{"id":7}' localhost:50051 Users/GetUser

Common mistakes

  • Changing field numbers in a proto (breaks compatibility).
  • Using gRPC directly from browsers without gRPC-Web.
  • Ignoring deadlines and timeouts.

Key takeaways

  • Typed RPC over HTTP/2 and protobuf.
  • Contract-first with generated code.
  • Great for internal services.

FAQ

gRPC vs REST?

gRPC is faster and typed but less human-readable and browser-friendly.

Does it support streaming?

Yes, four streaming modes.

More HTTP articles