Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Distinguish an entity identifier, an event identifier and a key for a repeatable operation. The first represents an object; the others help recognize a change or another attempt to execute the same intention. Define their scope, persistence and treatment of requests carrying the same key but different business content.
Illustrative example
Illustrative example: an integration requests order creation and loses the response. It retries while preserving the operation key. The receiver returns the recorded result instead of creating another order. If the amount has changed, reusing that key must not conceal the fact that the second request carries incompatible content.
Acceptance check
Send simultaneous and sequential duplicates, then simulate failure after saving the result. Also verify the policy after stored operation keys expire. Accept the design when one intention produces the agreed effect, conflicts remain visible and identifiers support investigation without relying on the object's business name, which may change or be shared.
Key takeaways
- Preventing duplicates requires stable operation identity and explicit rules for repeated requests.