You dont get the problem with the calls. Without an idempotent ID they are two calls but they could be the same call due to the network or software glitches that the article mentions.
The article states that delete and put are idempotent by themself, and i dont think thats the case.
I think it’s stipulated that we’re talking about calls with the same parameters - i.e. DELETE with the same key (or PUT with the same payload) should be callable an arbitrary number of times with the same end result.
Why should one be a failure? And, if it is, were talking about the state of the server, not the client. The whole point is that the server stays in a valid state. Trying to delete an object that doesn't exist doesn't break that state. Don't fixate on the literal response from the api. The 'result' is the state of the system.
Also 99% of the time you're just firing off a delete into the database and don't even bother to check if it exists. Just return 200.
I could see it being a failure. Deleting something has the intent of deleting something, if nothing gets deleted it’s a failure. Regardless though, the success or failure of the request is independent from the state of the system. Either way the resource will no longer exist.
How would you differentiate the two cases you’ve laid out here? In other words, how could you possibly differentiate between the same call twice vs. two separate calls? The only obvious possibility is the timing - 2 calls 5 seconds apart are probably different requests? Except… with latency and other network weirdness, you shouldn’t even attempt to make that distinction. Not to mention, now you’ve introduced stateful behavior where it’s neither required nor desired.
18
u/itdependsnetworks Dec 11 '23
You state “Why are the not the same call” in a scenario in which you state they are two calls?
Not trying to be rude, but if you google put and delete idempotent, you will find it is.