4 ms·
Having worked with some legacy subscription code it can be quite nasty. We had race conditions where we would charge users twice This has made me paranoid tha
by 4hg4ufxhy 2y ago
Having worked with some legacy subscription code it can be quite nasty.
We had race conditions where we would charge users twice
This has made me paranoid that any time I see timeout or error related to money I assume it went through and come back later.
- tk90 2y agoout of curiosity, what's the technical solution? My guess: add an idempotency key to the request and a message queue? Then when you try to consume it, you check whether that request was made previously.
- antifa 2y agoI tried subway online ordering once almost a year ago. The last final screen crashed and deleted the entire order from my cart. Anyways, you're probably wondering if the order actually went through but subway's UI was shit and nearly tricked me into replacing the same order a second time: yes.
- debugnik 2y agoA local cinema's shitty website charged me and, immediately after, my wifi disconnected for a few seconds. This somehow crashed their server entirely for several minutes, failing to send me the tickets even when it got back up. It took me several threatening emails to make them understand they had already taken my money and I wasn't going to try again until I got a refund. Now I'm paranoid any time I purchase online at mediocre shops.