Additional Notes
Why is dropping order-confirmation events usually unsafe?
Track: Java
Topic: Reactive Streams
Focus: Backpressure Strategies
Java: Backpressure Strategies
Answer
Because those events represent durable business facts that usually must not be lost.
A stream of order or payment events is not just a UI feed. If those events disappear under pressure, the system can lose correctness. Durable workflows usually need buffering, persistence, retries, or other reliability patterns instead of casual dropping.
A stream of order or payment events is not just a UI feed. If those events disappear under pressure, the system can lose correctness. Durable workflows usually need buffering, persistence, retries, or other reliability patterns instead of casual dropping.
Topics: Backpressure Strategies Java Reactive Streams