← All patterns
System architecture · Architecture pattern

Event-Driven architecture

Coordinate reactions to facts through explicit event contracts and delivery semantics.

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

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.

100%

Scroll to pan. Select a component for its role.

event driven architecture architectureCommitted 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 boundaryProjection consumerExternal-effect consumercommand → sql: commitsql → publisher: committed recordpublisher → bus: publishbus → projector: projection inputprojector → read: applybus → notifier: eventnotifier → provider: sendcommitcommitted recordpublishprojection inputapplyeventsendA command changes authoritative state before its fact is published.Order APIValidate a commandA local outbox or committed-change mechanism prevents a publish gap.Order SQLState + event recordThe publisher reads committed changes, with retry and progress handling.Committed publisherRelay / change captureDelivery, ordering and retention require explicit contracts.Event channelVersioned factsA delayed handler can leave its read model behind a successful command.Projection handlerVersion-aware applyQueries need a freshness policy for this representation.Read modelDerived stateAn accepted event is distinct from a completed external notification.NotificationhandlerStable event effectsAmbiguous provider acknowledgments need their own idempotency contract.External providerIndependent effectObserve end-to-end outcomes as well as publication.Event operationsSchemas, tracing, replay boundaries and consumer lag

Select a component, or focus it and press Enter, to read its role.

Walk through the design

Follow one operation

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.

Order producerActive in this stepEvent channelActive in this stepRead projectorWaitingNotification handlerWaiting
Step 1 of 3

Commit an operation

The producer records a business change and uses a reliable committed-change publication mechanism.

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.

Connect concept to practice

Related challenges

Browse challenges →

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.