Reactive Streams · interview question
Which statement correctly describes the role of backpressure in Reactive Streams?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamsthread-per-request-bottleneck
Answer and explanation
Correct answer
D. It controls the flow of data between Publisher and Subscriber
Why
Backpressure is a strategy to prevent the Subscriber from being overwhelmed by controlling the rate at which the Publisher sends data, ensuring the system remains stable and responsive.
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?