Reactive Streams · interview question
In a WebFlux application, why is it crucial to use non-blocking database drivers like R2DBC instead of traditional JDBC?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsblocking-the-event-loop
Answer and explanation
Correct answer
A. Traditional JDBC blocks threads, which can paralyze the limited thread pool.
Why
Traditional JDBC is blocking and can cause threads in the event loop to be tied up, leading to performance bottlenecks or server crashes. Non-blocking drivers like R2DBC allow the application to handle more concurrent operations without blocking.
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?