build-a-durable-idempotency-store
Build a durable idempotency store with scoped keys, request identity, atomic claims, outcome receipts, expiry, conflict handling, and recovery. Use when retried operations must not repeat side effects.
소스 정보
- 저장소
- protosphinx/sphinxstack
- 최근 소스 활동
- 2026년 7월 29일 13:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- build-a-durable-idempotency-store
- category
- code
- description
- Build a durable idempotency store with scoped keys, request identity, atomic claims, outcome receipts, expiry, conflict handling, and recovery. Use when retried operations must not repeat side effects.
# build-a-durable-idempotency-store
## When to use
- Use for payments, provisioning, messages, imports, or consequential mutation.
- Do not reuse keys across tenants, operations, or semantically different requests.
## Procedure
1. Define tenant, operation, key, request fingerprint, scope, and retention.
2. Atomically create pending ownership or return the existing state.
3. Reject key reuse with a different request fingerprint.
4. Record durable completed outcome before releasing ownership.
5. Handle crash, timeout, lease recovery, unknown external outcome, and manual reconciliation.
6. Encrypt sensitive results and bound storage, expiry, and abuse.
7. Test concurrency, duplicate, mismatch, crash windows, expiry, and disaster recovery.
## Failure plan
- Keep ambiguous external outcomes pending until reconciled rather than repeat them.
## Worked example
A payment timeout retains an indeterminate receipt and checks the provider before any retry.
## Done
- An idempotency implementation records scope, fingerprint, states, atomicity, outcomes, retention, security, and reconciliation
- Concurrent, mismatch, crash, timeout, external-unknown, expiry, tenant, and restore tests verify exactly-one effect
GitHub에서 보기