← All patterns The problem An order service directly coordinates every downstream reaction, coupling its latency and availability to other systems.
When it fits Consumers can react asynchronously and the team can operate event schemas, delivery, monitoring and recovery.
The whole architecture
Architecture diagram Download SVG Committed business changes feed a channel that supports independent read-model and notification reactions.
Blue arrows are calls and local writes; purple arrows are committed-event flow.
event driven architecture architecture Committed business changes feed a channel that supports independent read-model and notification reactions. Blue arrows are calls and local writes; purple arrows are committed-event flow. Producer transaction boundary Projection consumer External-effect consumer command → sql: commit sql → publisher: committed record publisher → bus: publish bus → projector: projection input projector → read: apply bus → notifier: event notifier → provider: send commit committed record publish projection input apply event send A command changes authoritative state before its fact is published. Order API Validate a command A local outbox or committed-change mechanism prevents a publish gap. Order SQL State + event record The publisher reads committed changes, with retry and progress handling. Committed publisher Relay / change capture Delivery, ordering and retention require explicit contracts. Event channel Versioned facts A delayed handler can leave its read model behind a successful command. Projection handler Version-aware apply Queries need a freshness policy for this representation. Read model Derived state An accepted event is distinct from a completed external notification. Notification handler Stable event effects Ambiguous provider acknowledgments need their own idempotency contract. External provider Independent effect Observe end-to-end outcomes as well as publication. Event operations Schemas, tracing, replay boundaries and consumer lag API / data call Event / job flowSelect a component, or focus it and press Enter, to read its role.
Event-driven coordination does not require an event-sourced domain. Independent consumer progress can make overall completion asynchronous. Walk through the design
Follow one operation Core flow Failure & recovery
Select a step to highlight its participants. This conceptual walkthrough is separate from challenge scoring.
Arrows show an event-driven variant with two interested consumers. Event-driven systems can use other channel and coordination arrangements.
1 Commit an operation2 Route the event3 Apply independent reactionsStep 1 of 3 Commit an operation The producer records a business change and uses a reliable committed-change publication mechanism.
← Previous Restart Next step →
Trade-offs to make explicit Producers can publish facts without waiting for every reaction, while end-to-end completion becomes asynchronous. Ordering, schema evolution, duplicates and observability require explicit contracts. A broker does not automatically provide business consistency. Failure modes to plan for A delayed consumer can expose an outdated projection after the originating command succeeds. Replayed or out-of-order events can duplicate an effect or restore stale data without identity and version rules. Before you build Explain your decision What does an accepted event prove, and how will a user learn whether all required reactions completed?
Use Plan & estimate inside practice to record your assumptions and trade-offs.
These links open the original challenges. Existing round unlocks, completions and points apply.
Rebuild search while writes continue Practice snapshot boundaries, committed changes, replay and projection recovery.
Open challenge → The phantom traffic spike Practice delayed and duplicate events with explicit result deadlines.
Open challenge → Further reading Microsoft · Event-driven architecture ↗
Original PractiseGrid explanations and conceptual diagrams, with primary references for further study. Dedicated scored exercises can be added as coverage grows.