Reactive Streams · interview question
How would you explain a critical consequence of using a blocking call, like Thread.sleep(), inside a WebFlux handler in an interview?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
A. It blocks the entire event loop, reducing throughput.
Why
Blocking the event loop with Thread.sleep() prevents it from handling other requests, drastically reducing throughput and potentially crashing the server under load.
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?