Recovering, Tracing and Monitoring

Recovering, tracing, and monitoring message-driven applications

A consumer crashes mid-handler. The Stripe webhook arrives twice. A notify-customer job fails forever and you can't tell why. Two workers race on the same aggregate and one's update gets silently overwritten. This section is the toolbox for everything that goes wrong after a message is dispatched.

Ecotone provides solutions across three concerns:

• Self-healing (Instant and Delayed Retries, Concurrency / Locking, Isolation of failures)
• Data Consistency (Resilient Message Sending, Outbox pattern, Message Deduplication)
• Recovery & Visibility (Dead Letter, Tracing, Monitoring)

To find out more about different use-cases, read related section about Handling Failures in Workflows.

Materials

Demo implementation

• Error Handling with delayed retries and storing in DLQ

Links

• Async Failure Recovery: Queue vs Streaming Channel Strategies [Article]
• Read in depth material about resiliency in Messaging Systems using Ecotone [Article]
• Resilient Messaging with Laravel [Article]
• Making your application stable with Outbox Pattern [Article]
• Handling asynchronous errors [Article]