Reactive Streams · interview question
How does the 'Flux' type in Project Reactor differ from 'Mono'?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamswebflux-vs-virtual-threads
Answer and explanation
Correct answer
C. Flux handles 0 to N items, while Mono handles 0 or 1 item.
Why
Flux is designed to handle streams of 0 to N items, allowing for potentially infinite streams, whereas Mono is used for scenarios where you expect 0 or 1 item, like a single result or completion signal.
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?