Reactive Streams · interview question
Which of the following scenarios is best suited for using the request(n) mechanism in Reactive Streams?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsbackpressure-strategies
Answer and explanation
Correct answer
A. When a subscriber needs to process data at a controlled rate to avoid memory overflow.
Why
The request(n) mechanism is crucial when a subscriber needs to control the rate of incoming data to prevent overwhelming its processing capacity and avoid memory issues.
Test yourself on Reactive Streams
A free test with instant, explained results. No account needed.
More Reactive Streams questions
- Which backpressure choice is usually most acceptable for a live price-ticker UI that only needs the newest value?
- Why can using onBackpressureDrop in a high-throughput system become a problem in production code?
- In Reactive Streams, what does a Publisher do?
- How does Project Reactor's Flux handle backpressure by default?
- How would you explain a key benefit of applying backpressure in a Reactive Streams system in an interview?
- When using Project Reactor's Flux, which method can be used to handle a scenario where data production exceeds the…