Reactive Streams · interview question
Why is it important for a reactive system to decouple the HTTP connection from the execution thread?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamsnon-blocking-i-o-event-loops
Answer and explanation
Correct answer
B. To allow the system to handle more concurrent connections.
Why
Decoupling the HTTP connection from the execution thread allows the system to efficiently manage resources and handle more concurrent connections, as threads are not blocked waiting for I/O operations to complete.
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?