Reactive Streams · interview question
When considering WebFlux for an e-commerce server, what is a primary benefit over traditional Spring MVC?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamsthread-per-request-bottleneck
Answer and explanation
Correct answer
D. Handles high concurrency with fewer threads
Why
WebFlux uses a non-blocking event-driven model that handles many concurrent requests with fewer threads compared to Spring MVC's thread-per-request model, improving scalability and resource efficiency.
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?