Idempotent Lambda Design
Because async and stream paths deliver at-least-once, every non-idempotent side effect (charge a card, send an email) can happen twice. Handlers must key work on a stable event identifier and use conditional writes or a deduplication table so a replayed event becomes a no-op instead of a duplicate.
This Concept is waiting for its first lesson!
Because async and stream paths deliver at-least-once, every non-idempotent side effect (charge a card, send an email) can happen twice. Handlers must key work on a stable event identifier and use conditional writes or a deduplication table so a replayed event becomes a no-op instead of a duplicate.
Are you a teacher? Sign in to start contributing.
Sign In