EDARELstill growing

Reliable messaging

Build publishers and consumers that stay correct when messages are duplicated, late, out of order or failing.

For Developers who know how queues, topics and partitions work and now need the system to survive real failures.

PrerequisitesEDA Event-driven foundations

9 notes, in order. Each one assumes the one before it. Still growing: more notes may be added.

Notes in this trail

Start the trail
  1. I · Living with failure
    Eventual consistency, not yet read
  2. Delivery guarantees, not yet read
  3. Idempotent consumers, not yet read
  4. Message ordering, not yet read
  5. II · When a message fails
    Retries and backoff, not yet read
  6. Dead-letter queues, not yet read
  7. Dead letters and ordered messages, not yet read
  8. III · Keeping two systems in step
    Outbox and inbox, not yet read
  9. Event versioning, not yet read