This two-day workshop takes a deliberate journey from foundational messaging concepts to the patterns required for real-world, production-grade systems. We’ll start with the simplest possible asynchronous designs—queues, events, and pub/sub—and progressively evolve them as new problems emerge: duplicates, message loss, scaling limits, partial failures, and long-running workflows.

Instead of presenting messaging patterns as a checklist, this workshop shows why each pattern exists, what breaks without it, and what trade-offs it introduces. Every step forward is motivated by a concrete failure mode.
Over two days, we’ll grow a system from:
“Messages get sent” to: “Messages survive crashes, retries, scaling, and time”
Patterns explored include:

- Queues, events, and pub/sub fundamentals
- Idempotent consumers and delivery guarantees
- Outbox and Inbox
- Competing Consumers and back-pressure
- Retries, poison messages, and dead-letter queues
- Sagas for long-running workflows
- Scatter-Gather coordination
- Claim Check, routing topologies, and messaging bridges

By the end of the workshop, you won’t just know these patterns—you’ll understand when you actually need them, when you don’t, and how to combine them without creating accidental complexity.