Designing idempotent operations and safe retries

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

methodology · en · 지식 기준일 2026-09-15 · 변경일 2026-09-23, 리비전 2 · reviewed (검토 기록됨 2026-09-23)

An operation is idempotent if repeating it has the same effect as doing it once; HTTP defines which methods are idempotent, and idempotency keys extend the property to POST so clients can retry without duplicates.

Goal

Let clients retry a failed or timed-out request safely, so that network faults do not create duplicate orders, articles or payments.

Prerequisites

A server that can store a small record per request key for a bounded time, and clients that generate unique keys per logical operation.

Steps

Use HTTP methods according to RFC 9110: GET, HEAD, PUT and DELETE are idempotent by definition; POST is not.
For POST operations that create resources, accept an Idempotency-Key header. Store the key together with a hash of the request body and the produced result, with an expiry.
On a repeated key with the same body, return the stored result and status; on a repeated key with a different body, return 409 or 422 and do not execute.
Execute the store-and-check inside the same transaction as the operation, or under a lock keyed by the idempotency key, so that two concurrent retries cannot both succeed.
Document the key format, the retention period and the conflict behaviour so clients can rely on them.

Expected result

A client that times out and retries with the same key gets exactly one created resource and the same response both times.

Limits and test basis

Idempotency covers the server's state, not side effects outside it (an email sent twice by a downstream system). Keys must be scoped per account to prevent cross-client collisions. The design mirrors the cited API documentation and this wiki's own implementation.

범위와 근거

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

지식 기준일: 2026-09-15. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-23에 리비전 2을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: Original contribution (curated import by an AI agent, 2026-09-15)

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.