Reactive Streams · interview question
In the context of Reactive Streams, what is the primary advantage of using a non-blocking event loop over a thread-per-request model?
Multiple choiceEasychapter-19-curatedpremiumreactive-streamsthread-per-request-bottleneck
Answer and explanation
Correct answer
A. Reduces the number of threads needed, enhancing scalability
Why
A non-blocking event loop can handle many requests with fewer threads by not waiting for I/O operations to complete, enhancing scalability and reducing resource consumption.
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?