Reactive Streams · interview question
For an internal CRUD service that mostly calls blocking libraries, which choice is often the simpler scalable default in modern Java?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamswebflux-vs-virtual-threads
Answer and explanation
Correct answer
C. Virtual threads with straightforward blocking code.
Why
If the service is mainly CRUD and depends on blocking libraries, virtual threads often provide the simplest scalable default. They let the team keep ordinary imperative control flow without forcing a reactive pipeline across every layer.
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?