Reactive Streams · interview question
How do WebFlux and Virtual Threads differ in handling concurrency for a high-load e-commerce server?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber
Answer and explanation
Correct answer
B. WebFlux uses an event-driven model, while Virtual Threads use a lightweight thread-per-request model
Why
WebFlux uses a non-blocking, event-driven model to handle concurrency efficiently, matching well with I/O-bound tasks. Virtual Threads, by contrast, use a lightweight thread-per-request model, making them suitable for tasks that can benefit from the traditional thread model but without the heavy resource usage.
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?