This website uses cookies to ensure you get the best experience.
Learn more.
A synchronous API must survive a slow downstream service without waiting indefinitely or consuming every worker. Which approach best fits?
Published
- Use a durable event identifier and idempotent consumer logic.
- Decouple producers and consumers using Pub/Sub.
- Apply bounded timeouts and a circuit breaker where appropriate.
- Use an idempotency key and persist the operation result atomically.
Comments — 0
Sign in to comment