Event-Driven Architecture
Event Driven Architecture
A design approach where systems trigger processing in response to events happening between them.
In Simple Terms
Event-driven architecture is a design where, when something changes between systems, that change signals the triggering of processing. Instead of services directly commanding each other, each service reacts independently to events that occur — that's the key characteristic. It's also sometimes used for things like sending order confirmation emails in online shopping, or notification systems on social media.
Behind the Name
This name combines three English words: "Event," meaning a happening, "Driven," meaning moved or powered by something, and "Architecture," meaning structure. Together they describe a structure where, when something changes between systems, that event triggers the next process to run.
Take a Closer Look!
Event-driven architecture is a design approach where, when an event—like "an order was confirmed" or "a file was uploaded"—occurs between systems, that event triggers the processing that needs to happen.
It places a mediator (such as an event broker) between the service that generates the event and the service that receives and processes it, so services can interact without directly commanding each other.
Because the service that generates an event and the service that receives it don't depend directly on each other, the whole system is less likely to grind to a halt if an error occurs in just one service, making it easier to build a setup that's resilient to change.
Depending on the event platform used, events can also be accumulated and processed asynchronously in batches later, which lets the system handle spikes in traffic more flexibly.
For example, this pattern is widely used in e-commerce sites: when an "order confirmed" event is published, it prompts services like payment processing, shipping, and notifications to each spring into action independently.