Idempotency Design Patterns

•
12
•

Provides expert architectural patterns for designing idempotent APIs and systems that handle retries safely without duplicate side effects.

This skill equips Claude with comprehensive strategies for building resilient distributed systems where operations must be executed safely across unreliable networks. It covers the implementation of idempotency keys, request fingerprinting, and database-level deduplication, ensuring that retries don't lead to double charges, duplicate orders, or data corruption. Whether you are architecting payment gateways, message queues, or RESTful APIs, this skill provides the implementation patterns needed to achieve reliable at-most-once and exactly-once processing semantics.

主な機能

01Deduplication strategies using Redis stores, database constraints, and optimistic locking
02Architectural guidance on handling in-flight requests and concurrent race conditions
03Implementation of Idempotency Key patterns and request fingerprinting techniques
04Domain-specific patterns for payments, order management, and event-sourced systems
0512 GitHub stars
06Safe retry logic for non-idempotent HTTP methods like POST and PATCH

ユースケース

01Building payment processing systems that prevent double-charging customers during network timeouts
02Refactoring legacy REST APIs to support robust client-side retry mechanisms
03Designing microservices that require exactly-once message processing and delivery