When would you pick gRPC over REST with JSON?

Answer

For internal service-to-service calls: compact binary Protobuf, HTTP/2 streaming, and generated, typed clients from one schema. Keep REST for public and browser APIs, where JSON is easy to read, HTTP caching works, and browsers cannot call gRPC without a proxy.

Review this in your daily deck → All cards in API design