This website uses cookies to ensure you get the best experience.
Learn more.
An event consumer may receive the same event more than once and must avoid duplicate database updates. Which approach best fits?
Published
- Use an idempotency key and persist the operation result atomically.
- Decouple producers and consumers using Pub/Sub.
- Use a durable event identifier and idempotent consumer logic.
- Apply bounded timeouts and a circuit breaker where appropriate.
Comments — 0
Sign in to comment