3 ms·
Exactly once processing != exactly once delivery
by shepherdjerred 2y ago
Exactly once processing != exactly once delivery
- ahoka 2y agoBut it’s mostly the processing that is interesting. Like this message I write now might see several retransmissions until you read it, but it’s a single message.
- frant-hartm 2y agoAnd on top of that this _end-to-end exactly-once guarantees_ makes the result look like the message was processed in the pipeline only once, while in reality a message will be processed 2x (or more times) in the pipeline in case of a temporary failure but only one version will be committed to the external system.