Reactive Streams · interview question
In a reactive application using WebFlux, what is the primary risk of calling Thread.sleep() inside the event loop?
Multiple choiceEasychapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
C. It blocks the event loop, causing latency and potential server crashes.
Why
Calling Thread.sleep() blocks the current thread, which is harmful in a non-blocking architecture like WebFlux. It can cause the event loop to stall, leading to increased latency and potentially crashing the server.
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?