Reactive Streams · interview question
Why is it dangerous to block an event loop when using a non-blocking framework like WebFlux?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
B. It can cause high latency and reduce throughput.
Why
Blocking an event loop in a non-blocking framework like WebFlux can lead to high latency and reduced throughput because it prevents other tasks from being processed. This can severely impact server performance and user experience.
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?