Event Driven Architecture is More Than Events

This talk will explore principles of event-driven architecture. Special consideration will be given to boundaries of responsibility, and the relationship of processes and data. Starting from events as the fundamental unit of communication, we'll explore how they impact the overall design of the system. Which communication patterns are a good match for events, and which are at odds with them? Specifically, we'll look at handling "unhappy" flows and duties of emitters and recipients of events. Progressing from there, we'll talk about long-running workflows and processes that involve several services, and usually, in DDD terminology, several bounded contexts. How do different approaches, such as orchestration and choreography, fit in, and how do we avoid building a "distributed monolith"?

Target Audience: Architects and Developers
Prerequisites: Some experience with microservices and messaging
Level: Basic