<sod>This [[architectural pattern]] may be applied by the design and implementation of applications and systems which transmit events among [[Loose coupling|loosely coupled software components]] and [[Service (systems architecture)|services]]. An event-driven system typically consists of event emitters (or agents), event consumers (or sinks), and event channels. Emitters have the responsibility to detect, gather, and transfer events. An Event Emitter  does not know the consumers of the event, it does not even know if a consumer exists, and in case it exists, it does not know how the event is used or further processed. Sinks have the responsibility of applying a reaction as soon as an event is presented. The reaction might or might not be completely provided by the sink itself. For instance, the sink might just have the responsibility to filter, transform and forward the event to another component or it might provide a self-contained reaction to such event. Event channels are conduits in which events are transmitted from event emitters to event consumers. The knowledge of the correct distribution of events is exclusively present within the event channel. The physical implementation of event channels can be based on traditional components such as [[message-oriented middleware]] or point-to-point communication which might require a more appropriate {{clarify-span|transactional executive framework|date=September 2013}}.<eod>
<sod>This [[architectural pattern]] may be applied by the design and implementation of applications and systems which transmit events among [[Loose coupling|loosely coupled software components]] and [[Service (systems architecture)|services]]. An event-driven system typically consists of event emitters (or agents), event consumers (or sinks), and event channels. Emitters have the responsibility to detect, gather, and transfer events. An Event Emitter  does not know the consumers of the event, it does not even know if a consumer exists, and in case it exists, it does not know how the event is used or further processed. Sinks have the responsibility of applying a reaction as soon as an event is presented. The reaction might or might not be completely provided by the sink itself. For instance, the sink might just have the responsibility to filter, transform and forward the event to another component or it might provide a self-contained reaction to such event. Event channels are conduits in which events are transmitted from event emitters to event consumers. The knowledge of the correct distribution of events is exclusively present within the event channel. The physical implementation of event channels can be based on traditional components such as [[message-oriented middleware]] or point-to-point communication which might require a more appropriate {{clarify span|transactional executive framework|date=September 2013}}.<eod>