Reactive Streams · interview question

When is Spring WebFlux usually a better fit than plain blocking code on virtual threads?

Multiple choiceEasychapter-19-curatedpremiumreactive-streamswebflux-vs-virtual-threads

Whenever the application performs simple CRUD against a blocking JDBC driver.Whenever the codebase already depends on synchronized blocks.Whenever the team wants shorter stack traces and easier debugging.When the workload is stream-heavy or keeps many slow connections open concurrently.

Answer and explanation

Correct answer

D. When the workload is stream-heavy or keeps many slow connections open concurrently.

Why

WebFlux is usually strongest when the workload is genuinely stream-shaped or connection-heavy, such as live feeds or many slow concurrent connections. For ordinary request-response CRUD code, virtual threads often preserve simpler control flow while still scaling well.

Test yourself on Reactive Streams

A free test with instant, explained results. No account needed.

Start free test

All Reactive Streams questions →

When is Spring WebFlux usually a better fit than plain blocking code on virtual threads?

Correct answer

Why

More Reactive Streams questions