Anti-patterns for event-driven architectures

More and more software projects are relying on event-driven architectures. However, their complexity is often underestimated. This results not only from technical challenges, but also from the fact that there are many different ideas about what an event-driven architecture actually is.

On the one hand, these ideas can lead to problems during operation; on the other hand, evolving such a system poses new challenges. Based on our own painful experiences in projects and partly similar experiences of our colleagues, we have anti-patterns that either result from different views and their implementation or that can make the maintaining such a system more difficult. In this talk, we present these anti-patterns, show what problems they cause and how they can be avoided.

Value for the audience:
Our talk is about various antipatterns that we have observed over the last 5 years in various projects in the area of event-based communication in large distributed systems, event sourcing-based systems and modeling of software systems using events (event modeling, event storming, etc.). We want to report on the ones we have often encountered and which had the biggest negative effect on the project, so that participants can easily avoid these problems.

Problems addressed:
The positive property of loose coupling can be negatively affected by wrong event or general interaction design, undermining one of the biggest advantages of an EDA. In this talk, we will present scenarios that undermine these benefits and how to restore them.

Talk language: English
Level: Newcomer
Target group: Developer; Software Architects

Company:
Digital Frontiers GmbH & Co. KG

Frank Steimle