event-driven-design

Event-driven architecture decouples services by using pub/sub patterns and domain events for communication, enhancing system resilience and reducing direct dependencies between components. It enables independent service scaling and failure isolation.

Event storming is a collaborative technique used to map domain events before coding. It helps teams model domain events, establish naming conventions, and design event schemas by visualizing the system's workflow and identifying bounded contexts.

Choosing between choreography and orchestration for event-driven system design depends on your workflow complexity. A decision framework helps evaluate whether decentralized event chaining or a central coordinator better suits your system's resilience and coupling requirements.

Common event-driven architecture anti-patterns include tight coupling through synchronous events and event schema rigidity. Avoid these by applying domain event design best practices, utilizing pub/sub for zero-coupling, and documenting designs with an event design document template.

You should not use event-driven architecture when system communication requires strict transactional consistency or when workflow logic is too simple to justify pub/sub overhead. In these cases, synchronous request-response models often provide better operational simplicity.