🎶🎵 A new dev team adopted E-D-A
Got head of line blocking, on their very first day
Isn't it ironic, don't you think 🎶🎵

The last few years have seen widespread adoption of Event-Driven Architecture, supported by DDD practices such as event storming. But what does that orange sticky note become when we start implementing our design? Common implementation choices include event sourcing, streaming platforms like Kafka and queuing systems like RabbitMQ.

Unfortunately not every orange sticky note has the same operational needs, and many teams remain confused about the differences between these options, resulting in the selection of the wrong paradigm for their needs.

This can lead to unnecessary complexity & operational challenges such as head of line blocking, dropped messages, challenges dealing with failed messages, difficulty with adaptive scaling and inadvertently increasing coupling between services.

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 such as Kafka and queueing systems such as RabbitMq, Azure Service Bus & AWS SNS/SQS.

We’ll then look at ways to assess your orange 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.