Architecture Event Driven

Overview

Use this skill to design event-driven systems that remain correct under retries, delays, and partial failures.

Scope Boundaries

• Workflows span multiple bounded contexts or services asynchronously.
• Temporal decoupling is needed to improve autonomy or resilience.
• Integration churn is high and direct RPC coupling causes fragility.

Core Judgments

• Event semantics: fact versus command and ownership of meaning.
• Delivery guarantees: at-most-once, at-least-once, effectively-once patterns.
• Ordering strategy: global ordering, per-key ordering, or order independence.
• Recovery model: replay, dead-letter, compensating actions, and backfill.