Reactive Streams · interview question
In Project Reactor, what is a potential risk when using flatMap() in a reactive pipeline?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsthread-per-request-bottleneck
Answer and explanation
Correct answer
D. It can produce data out of order
Why
Using flatMap() can lead to data being emitted out of order because it processes elements concurrently and asynchronously, unlike map(), which maintains the order.
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?