# Event-Driven Architecture

> Parts of a system talk by sending out events. Other parts react to them.

**Field:** Software Development  
**Category:** Architecture  
**Also known as:** EDA, Event-Driven Design, Event-Based Architecture

## Think of it like

Think of it like a school bell. When it rings, each class knows what to do next.

## Definition

In event-driven architecture, parts of a system talk by sending events. An event is a short note that something happened, like an order was placed. The part that sends it does not know who is listening. Any number of other parts can react in their own way. This keeps the parts loosely coupled, but the flow of work is harder to follow.

## Example

When Lucy's shop gets an order, it sends an order placed event. The email service sends a receipt and the stock service lowers the count. Neither was called directly.

## Why it matters

New parts can join by listening for events. The code that sends them does not change.

## Common mistake

Using events for everything, so nobody can tell what happens after a click. Keep a map of who sends and who listens.

## Three principles

- **Announce, do not call.** Something happened.
- **Many can react.** Sender does not know who.
- **Harder to trace.** Keep a map.

## Related terms

- [Publish-Subscribe (Pub/Sub)](https://learn.benibix.com/term/development/publish-subscribe)
- [Message Queue](https://learn.benibix.com/term/development/message-queue)
- [Event Bus](https://learn.benibix.com/term/development/event-bus)
- [Coupling](https://learn.benibix.com/term/development/coupling)

---

Source: https://learn.benibix.com/term/development/event-driven-architecture
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
