Reactive Streams · interview question
How does backpressure control the data flow in Reactive Streams?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber
Answer and explanation
Correct answer
B. Through a demand-based mechanism where Subscribers request a specific number of items
Why
Backpressure in Reactive Streams is controlled through a demand-based mechanism where Subscribers explicitly request a specific number of items they can handle. This ensures that the Publisher does not overwhelm the Subscriber with more data than it can process.
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?