Reactive Streams · interview question
In a WebFlux application, what is a potential consequence of blocking the event loop with a synchronous operation?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
D. The server can become unresponsive, affecting all users.
Why
Blocking the event loop with synchronous operations can make the server unresponsive, as it prevents the event loop from processing other tasks. This can affect all users connected to the server, causing timeouts and potential server crashes.
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?