Reactive Streams · interview question
What does the request(n) method in the Subscriber interface indicate?
Multiple choiceEasychapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
B. It requests the Publisher to emit n more items.
Why
The request(n) method is used by the Subscriber to request n more items from the Publisher. This is a core mechanism for implementing backpressure, allowing the Subscriber to control the flow of data based on its capacity.
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?