Reactive Streams · interview question
Why is dropping order-confirmation events usually a bad backpressure strategy?
Multiple choiceEasychapter-19-curatedpremiumreactive-streamsbackpressure-strategies
Answer and explanation
Correct answer
D. Because those events represent durable business facts, not replaceable UI noise.
Why
Order confirmations and similar business events are durable facts that usually must not be lost. Backpressure strategy depends on the semantics of the stream: replacing old price ticks may be acceptable, but dropping workflow events can break correctness.
Test yourself on Reactive Streams
A free test with instant, explained results. No account needed.
More Reactive Streams questions
- Which backpressure choice is usually most acceptable for a live price-ticker UI that only needs the newest value?
- Why can using onBackpressureDrop in a high-throughput system become a problem in production code?
- In Reactive Streams, what does a Publisher do?
- How does Project Reactor's Flux handle backpressure by default?
- How would you explain a key benefit of applying backpressure in a Reactive Streams system in an interview?
- When using Project Reactor's Flux, which method can be used to handle a scenario where data production exceeds the…