gRPC.
Two services that studied the same rulebook once, then speak in dense shorthand forever after.
- Dear server: users, please.1
JSON spells out every field name inside every message — that self-description is exactly what makes it readable.
- Page two of the request…2
The readability is paid for on both ends, in bytes shipped and in time spent parsing text.
- Same book, both of us.3
The .proto file is the single agreement both sides compile from, so a field cannot quietly mean two things.
- Says plenty, weighs nothing.4
With names settled in advance, the wire carries only values — a fraction of the bytes, decoded without guessing.
- getUser(42). Done.5
Generated stubs hide the network entirely; the remote call sits in your code like any local function.
- Is this… math?6
Outsiders never learned the rulebook — a browser needs a translating proxy to join this conversation.
Semicolony semicolony.dev/eli5/grpc/comic