Distributed Write Atomicity

Design the intermediate state, redelivery, and deduplication explicitly whenever two effects cannot share one transaction — a DB write plus an event/webhook/second-service call, a payment plus a notification, a state change plus a cache invalidation. Use whenever an operation must affect two systems that don't share a transactional authority. Trigger on "dual write", "outbox pattern", "idempotency key", "exactly-once", "duplicate event", "webhook delivery", "the payment charged twice", "publish an event after saving", "call another service after committing". Sibling of atomic-state-mutation — that skill covers multi-write atomicity inside one transactional authority; this one covers the case where no shared COMMIT exists at all.

annatchijova Updated 9 repo stars

File contents

annatchijova/skills commit ded9374bbc

Frequently asked questions

npx get-skill add annatchijova/distributed-write-atomicity