Pub/Sub is where many systems start. Messaging patterns are how they survive production. Publish/Subscribe is often the first step teams take when moving toward asynchronous, message-driven systems. It feels simple, flexible, and decoupled—but real-world systems quickly expose its limits. Duplicates happen. Messages get lost. Workflows stall halfway through. Failures don’t disappear; they become harder to reason about. This full-day workshop is about what comes after pub/sub. Through a series of practical scenarios, we will explore the messaging patterns that experienced teams rely on to build reliable, observable, and operable distributed systems. We will move beyond theory to examine why these patterns exist, when to apply them, and the trade-offs they intentionally entail. You’ll work through concrete problems such as: - Preventing data loss without distributed transactions - Coordinating long-running business workflows across services - Scaling consumers safely under load - Routing messages based on intent, not just topics - Making failures recoverable instead of catastrophic And we will achieve these by learning and working through patterns like: - Outbox and Idempotency - Sagas (orchestration vs choreography) - Scatter-Gather - Claim Check and large message handling We will also learn about routing topologies and discuss operational safety nets. By the end of the day, you will be able to: - Recognise the failure modes of naïve pub/sub systems - Choose the right messaging pattern for a given problem - Design workflows that survive crashes, retries, and partial failures - Reason about consistency, throughput, and resilience with confidence - Apply messaging patterns deliberately