Event-driven-architecture (EDA) is a popular choice for organizations modernizing their legacy systems. The decoupling of architecture subsystems through events allows different parts of the system to evolve independently and teams to work more autonomously, reducing time-to-market and costs.

EDA is not just an end-state to aim for, it’s an approach that helps and accelerates with the migration from your legacy to new architecture. As your modern and legacy systems run in parallel during the transition period, events are used to keep them synchronised, facilitating a gradual migration using patterns like the strangler fig.

But designing good events and choosing the most effective patterns is crucial to succeeding with EDA when modernizing. Doing this well requires a thorough understanding of your business and product, that’s why a domain-driven approach to EDA (DD-EDA) is vital.

This talk for developers, architects, and tech leaders covers the following topics

- CRUD events vs domain events
- event granularity
- legacy migration patterns
- shaping domain/service boundaries
- leading the design and decision making process
- implementation guidelines
- real world examples