Reactive Streams · interview question
When transitioning an e-commerce server from Spring MVC to WebFlux, what must be avoided to prevent server bottlenecks?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
A. Avoid using blocking libraries and operations.
Why
To prevent bottlenecks in a transition to WebFlux, it is essential to avoid blocking libraries and operations like traditional JDBC calls or Thread.sleep(). These can block the event loop, reducing server capacity and responsiveness.
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?