Reactive Streams · interview question
In a system using Project Reactor, what could be a consequence of using blocking operations on the event loop thread?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber
Answer and explanation
Correct answer
B. Decreased system throughput and responsiveness
Why
Using blocking operations on the event loop thread can lead to decreased system throughput and responsiveness. The event loop is designed to handle non-blocking tasks efficiently, and blocking it can cause delays and unresponsiveness in the system.
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?