Resiliency
Production resilience with retries, dead letter, outbox, and deduplication
Last updated
Was this helpful?
Production resilience with retries, dead letter, outbox, and deduplication
Works with: Laravel, Symfony, and Standalone PHP
A failed HTTP call crashes your handler. A duplicate webhook triggers double-processing. You've wrapped handlers in try/catch blocks and retry loops — each one slightly different. Error handling is scattered across your codebase with no consistent strategy.
Ecotone handles failures at the messaging layer — not per feature. Automatic retries, error channels, dead letter queues, the outbox pattern, and idempotency are configured once and apply to all handlers on a channel. When something fails, messages are preserved and can be replayed after the bug is fixed.
Explore the resiliency features:
Retries — Automatic retry strategies for transient failures
Error Channel and Dead Letter — Store failed messages for later replay
Final Failure Strategy — What happens when all retries are exhausted
Idempotency (Deduplication) — Prevent double-processing
Resilient Sending — Guaranteed delivery to async channels
Outbox Pattern — Atomic message publishing with database transactions
Concurrency Handling — Optimistic and pessimistic locking
Last updated
Was this helpful?
Was this helpful?