|
|
|
|
|
|
by saltcured
38 days ago
|
|
|
FWIW, I enjoyed your engagement throughout the thread above, fighting the good fight. I think there is also a risk of an "easy API" when it leads to magical thinking and sloppy development. If the naive client programmer starts to think the reliability is handled for them, they may also flub the handling of the idempotence key that remains the crux here. E.g. not persisting them well enough and returning to a situation where the user can accidentally make duplicate payments just like the naive system with no idempotence feature... |
|
|