Practise the standard verbs for handling backpressure in gRPC streams.
0 / 5 completed
1 / 5
Fill in: 'We ___ backpressure on a server-streaming RPC so a slow client can't be flooded faster than it can actually consume messages.'
We 'apply backpressure' — the standard, established streaming collocation for slowing a producer to match a consumer's rate. The other options aren't the recognised term here.
2 / 5
Fill in: 'Ignoring flow control signals on a stream can ___ the server buffering unbounded messages in memory for a slow reader.'
We say ignoring flow control will 'cause' unbounded buffering — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the number of unacknowledged messages in flight so a stream never gets more than a bounded window ahead of the reader.'
We 'limit a number' — the standard, simple collocation for capping an in-flight quantity. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the stream when the client's read buffer stays full past a timeout, rather than let messages queue forever server-side.'
We 'close a stream' — the standard, simple collocation for terminating a connection under a defined condition. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ buffer depth on both ends of a stream so a growing backlog is visible long before it causes an out-of-memory crash.'
We 'monitor' depth — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.