Reactive Streams · interview question
How does the 'request(n)' method in Reactive Streams help manage backpressure?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
A. It limits the number of items a Subscriber can process.
Why
The request(n) method allows a Subscriber to specify how many items it can handle at a time, helping prevent overwhelming the consumer with too much data at once.
Test yourself on Reactive Streams
A free test with instant, explained results. No account needed.
More Reactive Streams questions
- Why is it essential to avoid legacy JDBC in a reactive WebFlux application?
- What would be the effect of calling request(Long.MAX_VALUE) on a Subscription?
- Why does a Subscriber in the Reactive Streams specification matter in this design?
- How would you explain a key difference between WebFlux and virtual threads for handling concurrency in an interview?
- Which method in a Subscriber handles the completion signal from a Publisher?
- How do Virtual Threads in Project Loom aim to simplify concurrent programming compared to WebFlux?