gRPC Services

gRPC excels at internal service-to-service traffic: typed contracts, streaming, fast wire format. The trap is treating proto files like a generated artifact instead of a versioned contract.

When to use

• Internal service mesh / microservices.
• Mobile clients with poor network conditions (HTTP/2 multiplexing helps).
• Polyglot environments (Go server, TS/Python/Java clients).
• High-throughput RPC where JSON serialization is the bottleneck.

When NOT to use

• Public web API consumed from browsers — gRPC-Web exists but adds friction. REST or GraphQL is better.
• Browsers as clients in general — limited tooling.
• Simple internal API in a single language — REST/tRPC is faster to ship.

Proto layout