Reactive Streams · interview question
Which backpressure choice is usually most acceptable for a live price-ticker UI that only needs the newest value?
Multiple choiceMediumchapter-19-curatedpremiumreactive-streamsbackpressure-strategies
Answer and explanation
Correct answer
A. Drop or replace older values so the subscriber keeps the latest view.
Why
For a live UI that mainly cares about the newest state, dropping or coalescing stale ticks is often acceptable. This is a product-level decision: losing old view updates may be fine, while buffering everything can create unnecessary memory pressure.
Test yourself on Reactive Streams
A free test with instant, explained results. No account needed.
More Reactive Streams questions
- 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…
- In a non-blocking system using Reactive Streams, why is blocking the event loop a concern?