Reactive Streams · interview question
Why might you bound flatMap() concurrency when calling a downstream pricing service?
Multiple choiceHardchapter-19-curatedpremiumreactive-streamsfunctional-pipelines-flatmap
Answer and explanation
Correct answer
B. To avoid flooding the downstream service with too many concurrent requests.
Why
Unbounded flatMap() fan-out can overwhelm databases or downstream HTTP services. Bounding concurrency is part of reliability because it limits how much parallel work the pipeline can create at once.
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?