Event-driven architecture

Services communicate by emitting facts that happened, such as OrderPlaced, instead of calling each other. Coupling drops and new consumers are easy to add, but end-to-end flows become harder to follow.

Where it shows up in real systems

  • Pub/sub topic

    Producers publish once without knowing who listens; each subscriber processes the event independently. Fan-out multiplies downstream load by the number of subscribers.

    In production: Amazon SNS, Google Cloud Pub/Sub, Azure Event Grid, NATS

See it break, then fix it

Build an architecture, send it a day of traffic and outages, and learn why it holds or fails. Free to start.

Open the learning path Open the sandbox