Concept / Term · Established
EDA
A system design where producers publish events and independent consumers react to them, often asynchronously and close to real time.
Field note
In an event-driven architecture, components publish facts that have happened and other components react to them. The publisher does not need to know every consumer or wait for all resulting work to finish.
The approach develops the older ideas of messaging and event processing into an architectural style suited to loosely coupled, distributed systems.
An “order placed” event might independently trigger payment, stock reservation, analytics and customer notifications.
Loose coupling helps systems evolve independently, but teams must design for duplicate, delayed and out-of-order events.
In a sentence“Checkout publishes the order event; fulfilment and email subscribe to it.”
← View all 20 Writing Code: Tools, Languages & Building Blocks terms