Re:Idempotency Is Easy Until the Second Request Is Different
by hn_throwaway_99 on Sunday May 10, 2026 @03:14PM
(#48086889)
That is my point. When you are doing "normal" idempotency where you do the appropriate locking and keep around a table with ongoing request status and the result that you can return on a subsequent duplicate request, you handle all these cases. But in your "409" version of it, you haven't really saved much complexity on the server because you still need to keep around all that info if you're not just returning a 409 if you get a second request while the first is in progress.
[ Parent
| on HN ]
Re:Idempotency Is Easy Until the Second Request Is Different
by stickfigure on Tuesday May 12, 2026 @01:19AM
(#48104485)
I don't understand what you're saying. I can take any cheap rdbms, put a unique constraint on a column, and make my API return 409 for conflict vs 200 on success. There's so little code involved that it's embarrassing to charge money for it.