A synchronous API must survive a slow downstream service without waiting indefinitely or consuming every worker. Which approach best fits?

Published
  1. Use an idempotency key and persist the operation result atomically.
  2. Use a durable event identifier and idempotent consumer logic.
  3. Decouple producers and consumers using Pub/Sub.
  4. Apply bounded timeouts and a circuit breaker where appropriate.

Comments — 0