Event bus is a design pattern that acts as a communication channel between different components in a system, allowing them to exchange messages without being tightly coupled. It's like a party line for your application, where everyone can gossip about what's happening without directly talking to each other.

How to use it in a sentence

I was trying to figure out why my new feature wasn't working, and then I realized I forgot to publish the event on the event bus. Rookie mistake, I know.

My microservices are like a bunch of teenagers who refuse to talk to each other directly, so I had to set up an event bus to keep them from driving me insane.

If you actually want to learn more...

• Martin Fowler dives into the different meanings of "event-driven" and identifies useful patterns like event notification and event-carried state transfer. Read more

• Martin Kleppmann explores the benefits of event streams, including loose coupling, scalability, and flexibility, and how they relate to stream processing, event sourcing, and reactive systems. Check it out

• For a broader perspective on application architecture principles, including presentation-domain separation and resource pools, browse through Martin Fowler's collection of articles. Geek out here

Note: the Developer Dictionary is in Beta. Please direct feedback to skye@statsig.com.