Reactive Streams · interview question
What potential issue arises from blocking operations within a WebFlux event loop?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamswebflux-vs-virtual-threads
Answer and explanation
Correct answer
B. The event loop can become unresponsive, reducing system throughput.
Why
Blocking operations within a WebFlux event loop can cause the loop to become unresponsive, as it waits for the blocking task to complete. This can reduce throughput and negate the benefits of a non-blocking architecture.
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?