It's like 10,000 streams when what you need is a queue

🔗Why attend?

The last few years have seen widespread adoption of Event-Driven Architecture, supported by DDD practices such as event storming. But what happens to those orange sticky notes when we implement our design? Common choices include event sourcing, streaming platforms like Kafka, and queuing systems like RabbitMQ. Unfortunately, not every sticky note has the same operational needs, and teams often select the wrong paradigm, leading to unnecessary complexity, such as: head of line blocking, dropped messages, failed message handling challenges, adaptive scaling difficulties, and unintended service coupling.

In this talk, we’ll bring that orange sticky note into the runtime of our system. We’ll start with a deep dive into the similarities and differences between event streaming platforms (Kafka) and queueing systems (RabbitMQ, Azure Service Bus, AWS SNS/SQS). Then we’ll look at methods for assessing your sticky notes to work out which messaging and persistence paradigms suit each one, helping you build more resilient, scalable, and loosely coupled event-driven architectures.

🔗In this webinar you’ll learn to:

• Distinguish when to use queues, event streams, or event stores based on their operational characteristics.
• Recognize common messaging anti-patterns that lead to coupling, scaling bottlenecks, and operational complexity in distributed systems.
• Evaluate the trade-offs between messaging technologies such as Kafka, RabbitMQ, Azure Service Bus, and AWS SNS/SQS for different workloads.
• Translate domain events into production-ready messaging patterns by selecting the right delivery and persistence model for each use case.
• Design more resilient, scalable, and loosely coupled event-driven systems by matching messaging infrastructure to business and operational requirements.