 - An event-driven architecture is a software architecture pattern that orchestrates behavior around the production, detection and consumption of events as well as the responses they evoke. In this context, an event should be understood as some message, token, count, pattern, value, or marker that can be identified within an ongoing stream of monitored inputs, such as network traffic, specific error conditions or signals, thresholds crossed, counts accumulated, and so forth.
Event-driven architectures usually consist of event producers and event consumers. Event consumers subscribe to some kind of overarching event manager and event producers publish to this same manager. When the manager receives an event from a producer, it forwards that event to all registered consumers or stores the event for later forwarding, if a consumer is unavailable to receive the forward.
The benefits of event-driven architectures is that they enable arbitrarily large collections of consumers and producers, along with some number of managers, to exchange ongoing status and response information. They are also usually fairly responsive to events as they occur, and work well in unpredictable and loosely coupled (asynchronous) communication environments.
| LAST UPDATED: |
25 Sep 2007
|
 |
Read more about event-driven architecture:
|
|
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
 |
 |
| |
RELATED GLOSSARY TERMS
| Terms from Whatis.com − the technology online dictionary |
 |
business event management
(SearchSOA.com)
Business event management is the practice of incorporating business logic into labeling events, communicating events and handling events......
|
|
complex event processing
(SearchSOA.com)
Complex event processing (CEP) is the use of technology to predict high-level events likely to result from specific sets of low-level factors......
|
|
|
