Question 1

True or false: gRPC only supports unary request-response calls, not streaming.

Accepted Answer

False. gRPC supports four modes: unary, server streaming, client streaming, and bidirectional streaming—all built on HTTP/2.

Question 2

True or false: gRPC can automatically generate client and server code from a .proto file.

Accepted Answer

True. Using Protocol Buffers, gRPC generates stubs and skeletons in multiple languages (e.g., Go, Python, Java) from a single .proto definition.

Question 3

True or false: gRPC was originally developed by Google for internal microservices communication.

Accepted Answer

True. Google created gRPC to connect their own services efficiently. It was later open-sourced in 2015 as a general-purpose RPC framework.

Question 4

True or false: gRPC requires HTTP/2, making it incompatible with older web infrastructure.

Accepted Answer

True. gRPC natively uses HTTP/2 for multiplexing and streaming, so it won't work over HTTP/1.1 or older servers without a proxy.

Question 5

True or false: gRPC messages are human-readable by default, like JSON.

Accepted Answer

False. gRPC uses Protocol Buffers (binary format) by default, not JSON. It's compact and fast but not human-readable without tools.

Question 6

True or false: gRPC is slower than REST because it adds overhead with binary encoding.

Accepted Answer

False. gRPC is often faster than REST due to compact binary Protobuf and HTTP/2 multiplexing, reducing latency and bandwidth.

Question 7

True or false: gRPC can be used with WebSockets for real-time browser communication.

Accepted Answer

False. gRPC-Web exists for browsers, but it doesn't use WebSockets; it relies on HTTP/1.1 or HTTP/2 with limited streaming support.

Question 8

True or false: gRPC supports deadline propagation across service calls, enabling distributed timeouts.

Accepted Answer

True. gRPC allows setting deadlines that automatically propagate through chained RPCs, ensuring consistent timeout behavior across microservices.

gRPC Trivia Questions