This website uses cookies to ensure you get the best experience.
Learn more.
A stream consumer crashes after processing an event but before checkpointing. What must downstream processing tolerate?
Published
- Losing the entire stream's history automatically.
- A guarantee that business effects are automatically rolled back on consumer death.
- Assuming every replay represents fraudulent traffic.
- Re-reading an event and safely suppressing or reconciling duplicate effects.
Comments — 0
Sign in to comment