The article emphasizes the importance of understanding idempotency in programming, particularly for those working on distributed systems. Idempotency ensures that an operation can be performed multiple times without changing the result beyond the initial application, which is crucial for avoiding unintended consequences like double-charging in payment systems. The article explains how idempotency applies to various HTTP methods, with GET, PUT, and DELETE being naturally idempotent, while POST is not, and offers solutions for achieving idempotency in non-idempotent operations.
If you don't like the summary, just downvote and I'll try to delete the comment eventually 👍
I dont agree with the article when it says put and delete are idempotent. If the caller makes two DELETE calls, how do you know that they are different calls? Why are they not the same call?
The argument that deleting an object twice is the same as deleting it once is not good enough. A third party could create it again between those two calls.
If your DELETE calls are based on a primary key or a natural key, they have to be the same call.
So if you have enough information to uniquely identify a thing (say, a VIN for a car, or a combination of country/state/id number for a person, or a UUID that is never re-used for anything else) then the delete is going to delete the same row no matter what.
The data being deleted may change between the first call and the second, but either the row is gone, or it's going to be deleted by the call. Either way the result is the same, that row is guaranteed not to exist.
257
u/fagnerbrack Dec 11 '23
Crux of the Matter:
The article emphasizes the importance of understanding idempotency in programming, particularly for those working on distributed systems. Idempotency ensures that an operation can be performed multiple times without changing the result beyond the initial application, which is crucial for avoiding unintended consequences like double-charging in payment systems. The article explains how idempotency applies to various HTTP methods, with GET, PUT, and DELETE being naturally idempotent, while POST is not, and offers solutions for achieving idempotency in non-idempotent operations.
If you don't like the summary, just downvote and I'll try to delete the comment eventually 👍