Reactive Streams · interview question
When using Project Reactor, why is it important to avoid blocking operations on the event loop?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber
Answer and explanation
Correct answer
A. It can degrade the responsiveness of the application.
Why
Blocking operations on the event loop can severely degrade the responsiveness of a reactive application. The event loop should remain free to handle incoming events efficiently, and blocking it prevents this, leading to potential performance bottlenecks.
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?