The idea
A caller can lose the response after a server has already completed an operation. Retrying is then ambiguous: the first attempt may have succeeded. Idempotency gives repeated attempts a defined relationship instead of leaving duplicates to later cleanup.
Design choice
Associate a client-supplied operation key with a bounded, durable result. Reject reuse of the same key with conflicting inputs. Keep the retention interval long enough for expected retries and document what happens when it expires.
Worked example
A form submission uses the same operation key after a connection timeout. The service returns the earlier result instead of creating a second ticket.
Before you ship
- Test a lost successful response
- Reject conflicting key reuse
- Document retention and expiry
Examples are illustrative. Adapt the checks to your own environment.