Reactive Streams · interview question
Why is it essential to avoid legacy JDBC in a reactive WebFlux application?
Multiple choiceEasychapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
D. It introduces blocking operations.
Why
Legacy JDBC is inherently blocking, which can stall the event loop in a reactive WebFlux application, leading to reduced performance and scalability issues.
Test yourself on Reactive Streams
A free test with instant, explained results. No account needed.
More Reactive Streams questions
- 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?
- In a WebFlux application, why is it crucial to use non-blocking database drivers like R2DBC instead of traditional JDBC?