Reactive Streams · interview question
Why does a Subscriber in the Reactive Streams specification matter in this design?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber
Answer and explanation
Correct answer
A. To request data from the Publisher
Why
In the Reactive Streams specification, a Subscriber requests data from a Publisher and processes the data it receives. The Subscriber controls the flow of data and ensures backpressure is handled.
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?
- 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?
- In a WebFlux application, why is it crucial to use non-blocking database drivers like R2DBC instead of traditional JDBC?