This website uses cookies to ensure you get the best experience.
Learn more.
A client retries a payment request after a network timeout. The server must avoid charging twice for the same logical operation. Which approach best fits?
Published
- Use an idempotency key and persist the operation result atomically.
- Decouple producers and consumers using Pub/Sub.
- Apply bounded timeouts and a circuit breaker where appropriate.
- Use a durable event identifier and idempotent consumer logic.
Comments — 0
Sign in to comment