Information Technology Reference
In-Depth Information
EDA
When working with events, we usually end up splitting the components involved in the
event management into three main categories:
• Components that are creating specific, simple events
• Components that are processing simple events into complex ones
• Components that are waiting for specific events
EDA defines a decoupled way to build an infrastructure based on these three components,
along with a way to communicate events between them. The following diagram depicts all
the components in an EDA working together:
The main components the architecture proposes are event producers, event consumers,
event processing agents, and event channels.
The sole responsibility of event producers is to generate streams of events. It is anything
that emits any sort of information, regardless of how complex or basic the information
might be. It can go from simple sensors to user interfaces to complex applications that can
send very specific notifications. If it can send an event to an external scope, it is an event
producer.
Event producers will need means to propagate their events to other components of the
EDA. Event channels are the component through which event producers will be able to do
so. Anything from a protocol definition to the logical representation of a wire between a
sensor and a computer could be considered an event channel, as long as events are trans-
mitted through that mean.
