Start With JSON Over HTTP

For modest internal traffic, JSON over HTTP is fine. You can call it with curl, read it in a browser and debug it with anything. gRPC earns its place between services that call each other thousands of times a second, where payload size, parsing cost and a shared contract start to matter.

gRPC is what you reach for when JSON-over-HTTP is too slow, too unstructured, or too one-directional. It's HTTP/2 (HTTP/3 is supported by Grpc.Net.Client as an opt-in or an alt-svc upgrade; HTTP/2 stays the default) + Protocol Buffers + code-generated stubs in the 12 languages grpc.io lists. It's a common choice for service-to-service traffic, with gRPC-Web bridging browsers and Connect-RPC offering a friendlier wire format.

The trade is real: Protobuf payloads are smaller and cheaper to parse than JSON and gRPC streams both ways, but you give up cache-friendly semantics, browser-native debugging, and easy curl. Use it inside the mesh; expose REST or GraphQL at the edge.

If internal calls are slow or fragile
  • Your service-to-service JSON costs more CPU than the business logic
  • You wrote the same DTO five times in five languages
  • You need bidirectional streaming and SignalR feels heavy
  • Your mobile team wants strongly-typed clients without OpenAPI codegen pain

Define once in .proto, generate everywhere, stream when you need to, fall back to JSON transcoding for the edge.