2 ms·
> That's why we don't say Sequin offers exactly-once delivery anywhere. We say it offers at-least-once delivery and exactly-once processing. The author should
by griffgeorge 2y ago
> That's why we don't say Sequin offers exactly-once delivery anywhere. We say it offers at-least-once delivery and exactly-once processing.
The author should note that the homepage at https://sequinstream.com/ https://sequinstream.com/ does in fact claim that Sequin supports "Exactly-once delivery" under the "Key features" heading.
- notfed 2y agoWell that doesn't seem consistent.
- _acco 2y agoAye, good catch! Honest mistake. Fixed.
- notfed 2y agoAck.
- rzzzt 2y agoI didn't get this one.
- notfed 2y agoFrom the site: > Exactly-once processing: Messages must be ack'd after they're delivered.
- rzzzt 2y agoFrom the submission: > For example, imagine when a worker processes a message, it performs > a side effect like sending an email. It very well could receive the > message, send the email, but then due to a network error fail to > acknowledge the message. Since we are now deeply in "explaining the joke"-territory: in this reply I am pretending to be a message queue implementation that never receives the ack from a receiver. Counting the vast number of upvotes on the comment, at least one other person was deligthed by this chain of replies with the subtext being apparent. I have also found your parent comment worthy of a sensible chuckle for the same reason.
- hinkley 2y agoThis is my new favorite video on TCP/IP: https://www.youtube.com/shorts/R6WN4_bBB1Q https://www.youtube.com/shorts/R6WN4_bBB1Q
- kortilla 2y agoOut of order does not cause a reset. Some networks with unstable topologies like wireless meshes frequently cause reordering and it doesn’t destroy TCP streams. It usually just results in inefficient retransmits when the receiver registers it as a drop. It was a good video until the RST.
- hinkley 2y agoI think that was supposed to be packets coming too fast. They kinda flubbed that bit.
- throwaway313373 2y ago[dead]