Idempotency
An idempotent operation has the same intended effect on system state when repeated identically as when performed once.
Idempotency means that repeating an identical operation has the same intended effect on system state as performing it once. Responses or logs do not have to be identical each time.
A fictional ERP call creates order W-240 with stable key shop-1:W-240:create. If the destination reliably recognises that key, retrying must not create a second order. Key scope, payload and retention must match the API's actual supported rules.
Sending a key provides no protection if the receiver ignores it. The HTTP method name alone also does not establish a business-correct integration. Idempotency describes repetition's effect; a retry strategy determines when another attempt occurs.
Sources
Related terms
- Retry strategyA retry strategy defines which failures to retry, the waiting intervals and the limit on further attempts.
- Server-sent eventsServer-sent events carry text notifications from server to client over HTTP, for example about the progress of a background job.
- Entity tagAn ETag identifies a particular representation version of an HTTP resource and supports conditional reads or changes.
- Cross-Origin Resource SharingCORS controls browser access to responses across origin boundaries. It replaces neither API login nor permission checks.
- Electronic Data InterchangeEDI transfers structured business documents between systems. Format, partner profile, data mapping and responses need to agree.
- Real-time processingReal-time processing handles arriving events against a defined latency target. Event time, processing time and late data need explicit rules.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.