Re:Idempotency Is Easy Until the Second Request Is Different
by hamdingers on Sunday May 10, 2026 @11:56AM
(#48084977)
If you're a client using the same idempotency key for a materially different request you have a bug.
[ Parent
| on HN ]
Re:Idempotency Is Easy Until the Second Request Is Different
by theptip on Sunday May 10, 2026 @12:54PM
(#48085564)
Yes, and if you are building a payment API you need to be robust to client bugs.
Re:Idempotency Is Easy Until the Second Request Is Different
by jeremyjh on Sunday May 10, 2026 @03:10PM
(#48086860)
The client is part of a distributed transaction. It can't be oblivious to this. Clear semantics and accurate adherence to them is the only answer that doesn't make the overall system unsound. Client bugs are expected and so the simplest semantics that ensure data integrity and accurate responses are the best way to help them identify and fix their bugs.