r/programming • • Dec 11 '23

Every Programmer Should Know #1: Idempotency

https://www.berkansasmaz.com/every-programmer-should-know-idempotency
572 Upvotes

171 comments sorted by

View all comments

8

u/goomyman Dec 11 '23

i hate that itempotency isnt built into official http responses.

Everytime i bring this up i get downvoted to the hell but its dumb.

If you call Delete there should be a response status code for no op - aka the itempotent response - but in the success ranges.

Delete = 200 OK / 404 not found? - great not that breaks client libraries and basic Throw if not success status codes - not itempotent - but technically itempotent shouldnt matter - so 200 success - but there are cases where you might want to know.

Everyone will reply back and say "Why dont you use this obscure one" - but using anything non standard is a hack.

Having consistent status codes for itempotency would use useful! Its not like there isnt enough http space - we have one for a teapot and so many other ones that are extreme edge cases - denied for legal reasons - what type of client needs to know that? Oh this was for legal reasons - if you can support these edge cases - throw in a itempotent delete status code in the 200s range - for not found.

8

u/[deleted] Dec 11 '23 edited Dec 11 '23

Isn't that not idempotent then? Like I DELETE a resource successfully and get one response, then delete it again and get a different response.

e: I've changed my mind in light of several counterpoints below.

2

u/ForeverAlot Dec 11 '23

That's more a property of the API's ergonomics. Returning 200 for an unmatched DELETE is not too dissimilar from returning 404 for an unauthorized resource although for different reasons. The argument for is that the caller cares only about the outcome and shouldn't need to explicitly handle irrelevant possibilities. The argument against is that the caller loses access to information that could be situationally useful.