Multiple ChoiceBeginner 45s
Exactly-Once vs At-Least-Once Semantics
In a distributed payment pipeline, what is the practical way to achieve exactly-once effects on top of an at-least-once transport?
Options
- 1Disable retries entirely in the transport layer so no message is ever duplicated
- 2Route every message through a single-threaded consumer to serialize processing
- 3Combine at-least-once delivery with idempotent processing keyed on a unique message id
- 4Buffer messages in process memory across restarts to deduplicate deliveries
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.