> In APIs, passively safe means failures (crashes, timeouts, retries, partial outages) can't produce duplicate work, surprise side effects, or unrecoverable state.
I thought that was what 'idempotent' meant.
It's mostly semantics. Passive safety is the "why" while idempotency is the "how".
> In APIs, passively safe means failures (crashes, timeouts, retries, partial outages) can't produce duplicate work, surprise side effects, or unrecoverable state.
I thought that was what 'idempotent' meant.
It's mostly semantics. Passive safety is the "why" while idempotency is the "how".