Server streaming: a single client request opens a stream over which the server pushes many messages, ideal for subscriptions, large result sets, or progress updates without polling.
2 / 5
What is client streaming in gRPC?
Client streaming: the client pushes a sequence of messages (e.g., uploading chunks or telemetry) and the server returns a single summary response after the stream closes.
3 / 5
What does bidirectional streaming allow?
Bidirectional streaming: client and server each read and write streams concurrently on one channel, enabling real-time interactive use cases like chat or live collaboration with full duplex flow.
4 / 5
Why does gRPC streaming benefit from being built on HTTP/2?
HTTP/2 multiplexing: multiple gRPC streams share a single TCP connection without head-of-line blocking at the application layer, making concurrent streaming calls efficient and avoiding many connections.
5 / 5
What is backpressure in the context of gRPC streams?
Backpressure: HTTP/2 flow control lets a slow consumer signal it needs the producer to pause, preventing unbounded buffering and memory blowups when one side cannot keep up with the other.