Reactive Streams · interview question
In a non-blocking architecture using Reactive Streams, what happens when a Subscriber requests more data than the Publisher can handle?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber
Answer and explanation
Correct answer
D. The Publisher will manage backpressure and send data as it becomes available
Why
The Publisher in a Reactive Streams setup is responsible for managing backpressure and will send data to the Subscriber as it becomes available, allowing the system to handle varying rates of data production and consumption without crashing or blocking.
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?