Problem
Paradox Shop's ledger-adjustment operation must land exactly once, no matter how many times the network or a crash forces a retry; neither a missed adjustment nor a duplicated one is acceptable. This is stricter than an ordinary at-least-once pipeline: it isn't enough to make the consumer merely tolerate duplicates. Design a pipeline from scratch that gets both the producer's delivery guarantee and the consumer's own correctness right.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.