News for hackers. Stuff that matters.
Re:Idempotency Is Easy Until the Second Request Is Different by ahoka on Sunday May 10, 2026 @07:21AM (#48082962)
So idempotency is easy if your service does not do anything useful?
Re:Idempotency Is Easy Until the Second Request Is Different by mrkeen on Sunday May 10, 2026 @08:20AM (#48083396)
It's just the horrible misapplication of the term 'stateless' to a wrapper around something very-much stateful. It's here to stay.

(Though I do disagree with the original premise too. Putting on a 'stateless' boxing glove won't mean there's no difference between punching a guy once or twice)

Re:Idempotency Is Easy Until the Second Request Is Different by zinkem on Monday May 11, 2026 @12:46AM (#48091142)
> Putting on a 'stateless' boxing glove won't mean there's no difference between punching a guy once or twice

There are still side effects in the system, of course.

But what your database looks like afterwards is the important part.

Can you recover lost data, replay transactions, undo, etc etc?

Re:Idempotency Is Easy Until the Second Request Is Different by zinkem on Monday May 11, 2026 @12:44AM (#48091128)
Whether or not your service does something useful is up to you.

A database on it's own is enough for most business applications.

If you haven't seen this yet, you're just rent seeking.