# Event Bus

> A shared line that takes events from senders to whoever wants them.

**Field:** Software Development  
**Category:** Architecture  
**Also known as:** Message Bus, Event Broker, Event Stream

## Think of it like

Think of it like a notice board in a school hall. Anyone can pin a note, and anyone can read it.

## Definition

An event bus is a shared channel that carries events to the parts that want them. Senders put events on the bus without knowing who will read them. Listeners tell the bus which kinds of event they care about. The bus passes each event to everyone who asked. It can live inside one app or run as a separate service between many.

## Example

In Emma's app, the cart puts an item added event on the bus. The badge counter and the suggestions panel both listen, and both update at once.

## Why it matters

It gives a system one place for events to flow. Parts do not have to wire into each other.

## Common mistake

Sending all things over the bus, even simple calls. Then finding a bug means guessing who did what.

## Three principles

- **One shared channel.** For all events.
- **Send without knowing.** Who will read it.
- **Listen by kind.** Only what you need.

## Related terms

- [Publish-Subscribe (Pub/Sub)](https://learn.benibix.com/term/development/publish-subscribe)
- [Event-Driven Architecture](https://learn.benibix.com/term/development/event-driven-architecture)
- [Message Queue](https://learn.benibix.com/term/development/message-queue)
- [Observer Pattern](https://learn.benibix.com/term/development/observer-pattern)

---

Source: https://learn.benibix.com/term/development/event-bus
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.
