Reactive Streams · interview question
Which of the following best describes the lazy nature of a reactive stream?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamspublisher-and-subscriber
Answer and explanation
Correct answer
A. It does nothing until subscribe() is called
Why
Reactive streams are lazy, meaning they do not start processing or emitting data until a Subscriber explicitly subscribes to the Publisher. This allows the system to remain efficient and avoid unnecessary computations.
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?