Reactive Streams · interview question
What role does the 'Subscriber' interface play in the Reactive Streams Specification?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
C. It processes data emitted by a Publisher.
Why
The Subscriber interface represents the consumer that receives and processes data from the Publisher, managing backpressure and handling data consumption asynchronously.
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?