3 ms·
> at least once semantics. > user code. A past life has taught me that users will never properly understand at-least-once semantics. Anytime you redeliver me
by londons_explore 3y ago
> at least once semantics.
> user code.
A past life has taught me that users will never properly understand at-least-once semantics. Anytime you redeliver messages, you will get a flurry of user complaints and breakage.
Either you do the impossible and invent a way to do exactly-once semantics. Or you should always redeliver 0.1% of all messages, just so that users don't come to depend on messages being delivered once.
- chewbacha 3y agoEarly SQS basically did this. I'm not sure if this was intentional or not but it quickly taught me to respect redelivery.
- plaguuuuuu 3y agoIf messages need to be idempotent, I definitely recommend creating integration tests to ensure this from the sending side :-)