Re:Idempotency Is Easy Until the Second Request Is Different
by pdonis on Monday May 11, 2026 @04:07PM
(#48099992)
Update: stickfigure basically answered this in another subthread: as I understand the answer, it is that you do check the idempotency key, but inside the DB transaction, so you have to start a new transaction on every request. If, inside the transaction, your idempotency key check shows that another request with that key was already received, you don't do anything to change the DB inside the transaction and just commit it as a no-op.
[ Parent
| on HN ]
There are no comments on this comment yet.