Reactive Streams · interview question
Why does the Publisher in the Reactive Streams Specification matter in this design?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
A. Emit data to a Subscriber according to demand.
Why
In the Reactive Streams Specification, the Publisher is responsible for emitting data items to the Subscriber based on the demand signaled by the Subscriber. This ensures backpressure and flow control.
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?