Event-Driven Architecture

Services emit events when something happens. Other services react without the emitter knowing who listens.

★ async

Flow From Map

OrderSvc → emit: OrderPlaced
          ↓ (anyone subscribed)
EmailSvc, InventorySvc react

Your POC Area

Replace this placeholder with your interactive proof of concept for Event-Driven Architecture. This route is already dedicated to this pattern, so you can add diagrams, controls, code demos, or simulations here.

Example references: Kafka, EventBridge, EventEmitter, eventemitter2

Domain Events

OrderService emits:

-> OrderPlaced { orderId, items, userId }

-> OrderCancelled { orderId, reason }

-> OrderShipped { orderId, trackingId }

Subscribers react:

EmailSvc listens -> OrderPlaced

AnalyticsSvc listens -> all events

InventorySvc listens -> OrderPlaced, OrderCancelled