Reactive Streams · interview question
In a reactive system using Spring WebFlux, how is the HTTP request handling different from a traditional server model?
Multiple choiceEasychapter-19-curatedpremiumreactive-streamsnon-blocking-i-o-event-loops
Answer and explanation
Correct answer
A. Requests are managed by a fixed number of event loop threads.
Why
Spring WebFlux uses a fixed number of event loop threads, typically one per CPU core, to manage HTTP requests. This model is non-blocking and allows efficient handling of concurrent requests.
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?