Which scenario is best suited for gRPC over REST?

Which scenario is best suited for gRPC over REST?

• A. Public-facing API with broad client support
• B. Static content delivery
• C. Internal service-to-service communication with high throughput using binary Protocol Buffers
• D. One-way event streaming

Answer: (C)

The scenario tests where to use gRPC versus REST based on how the communication will flow. gRPC is designed for efficient, high-throughput, low-latency service-to-service calls, using HTTP/2 and Protocol Buffers. The binary Protocol Buffers format is compact and fast to parse, and HTTP/2 brings multiplexing and strong streaming capabilities. This combination makes gRPC especially well-suited for internal microservice communication where many small, frequent calls happen between trusted services, and you want efficient contracts and potential for streaming. That’s why internal service-to-service communication with high throughput using binary Protocol Buffers is the best fit. REST is generally favored for public APIs with broad client support because JSON is human-readable and widely compatible, and for static content delivery you’d rely on standard web delivery mechanisms rather than RPC. Event streaming can be done with various streaming or messaging systems, where gRPC’s streaming is useful but not always the natural choice for one-way event streams.

The scenario tests where to use gRPC versus REST based on how the communication will flow. gRPC is designed for efficient, high-throughput, low-latency service-to-service calls, using HTTP/2 and Protocol Buffers. The binary Protocol Buffers format is compact and fast to parse, and HTTP/2 brings multiplexing and strong streaming capabilities. This combination makes gRPC especially well-suited for internal microservice communication where many small, frequent calls happen between trusted services, and you want efficient contracts and potential for streaming.

That’s why internal service-to-service communication with high throughput using binary Protocol Buffers is the best fit. REST is generally favored for public APIs with broad client support because JSON is human-readable and widely compatible, and for static content delivery you’d rely on standard web delivery mechanisms rather than RPC. Event streaming can be done with various streaming or messaging systems, where gRPC’s streaming is useful but not always the natural choice for one-way event streams.