Reactive Streams · interview question
How does Spring WebFlux's use of a non-blocking event loop increase scalability over a traditional thread-per-request model?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsnon-blocking-i-o-event-loops
Answer and explanation
Correct answer
B. By using fewer threads, it reduces context-switching overhead.
Why
Spring WebFlux's non-blocking event loop model uses fewer threads, thereby reducing the context-switching overhead associated with many threads in a traditional model. This allows handling more requests with the same resources.
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?