How Event Driven Architectures Go Wrong & How to Fix Them

This is an excerpt from a talk at the GOTO 2024 conference about how event-driven architectures can go wrong. The speaker, Matthew Meckes, first establishes the goals of event-driven architectures, which include scalability, agility, and fast feedback loops. Then, he introduces a series of anti-patterns, or common mistakes, that developers often encounter when building these architectures. These patterns, often characterized by a lack of communication and a reliance on "YOLO" (You Only Live Once) practices, can lead to significant technical debt and hinder the desired benefits of event-driven architectures. Meckes ultimately argues that the solution to these problems lies in a strong focus on domain-driven design, which fosters better communication and collaboration within development teams. By emphasizing communication and leveraging tools like event storming, developers can create more robust and scalable event-driven architectures.

There are no comments yet.

Please log in to write the first comment.