Which statement best describes gRPC usage?

Which statement best describes gRPC usage?

• A. The most popular RPC protocol, using Protocol Buffers for binary serialization and HTTP/2 for transport. It is significantly faster than JSON REST and generates type-safe client and server code in multiple languages from a single .proto definition.
• B. A RESTful interface designed around resources.
• C. A scripting language for defining endpoints.
• D. A text-based data interchange format used by GraphQL.

Answer: (A)

gRPC is a high-performance remote procedure call framework designed for fast, cross-language service-to-service communication. It uses Protocol Buffers for compact binary serialization and HTTP/2 for transport, which enables multiplexed streams, lower latency, and efficient communication. From a single .proto definition, you can generate type-safe client and server stubs in multiple languages, ensuring consistency across services. It also supports unary and streaming RPC patterns, making it versatile for different communication needs. This combination—binary serialization with Protocol Buffers, HTTP/2 transport, and generated type-safe code from one definition—best describes gRPC and sets it apart from REST-based designs, scripting languages for endpoints, or GraphQL approaches. REST emphasizes resources and JSON over HTTP, a scripting language is unrelated to how gRPC defines endpoints, and GraphQL centers on a query language rather than a binary, code-generated RPC mechanism.

gRPC is a high-performance remote procedure call framework designed for fast, cross-language service-to-service communication. It uses Protocol Buffers for compact binary serialization and HTTP/2 for transport, which enables multiplexed streams, lower latency, and efficient communication. From a single .proto definition, you can generate type-safe client and server stubs in multiple languages, ensuring consistency across services. It also supports unary and streaming RPC patterns, making it versatile for different communication needs.

This combination—binary serialization with Protocol Buffers, HTTP/2 transport, and generated type-safe code from one definition—best describes gRPC and sets it apart from REST-based designs, scripting languages for endpoints, or GraphQL approaches. REST emphasizes resources and JSON over HTTP, a scripting language is unrelated to how gRPC defines endpoints, and GraphQL centers on a query language rather than a binary, code-generated RPC mechanism.