Event driven architecture: Difference between revisions
From Cyborg Anthro Wiki
Caseorganic (talk | contribs) Created page with 'Event-driven architecture (EDA) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. An event can be defined as "a sign…' |
Caseorganic (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{stub}} | |||
===Definition=== | |||
Event-driven architecture (EDA) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. An event can be defined as "a significant change in state"[http://en.wikipedia.org/wiki/Event-driven_architecture#cite_note-0]. For example, when a consumer purchases a car, the car's state changes from "for sale" to "sold". A car dealer's system architecture may treat this state change as an event to be produced, published, detected and consumed by various applications within the architecture." [http://en.wikipedia.org/wiki/Event-driven_architecture]. | Event-driven architecture (EDA) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. An event can be defined as "a significant change in state"[http://en.wikipedia.org/wiki/Event-driven_architecture#cite_note-0]. For example, when a consumer purchases a car, the car's state changes from "for sale" to "sold". A car dealer's system architecture may treat this state change as an event to be produced, published, detected and consumed by various applications within the architecture." [http://en.wikipedia.org/wiki/Event-driven_architecture]. | ||
===External Links=== | |||
http://en.wikipedia.org/wiki/Event-driven_architecture | |||
Latest revision as of 23:11, 4 February 2011
This article is a stub! It is in draft form while it undergoes peer review. You can help CyborgAnthropology.com by expanding or providing feedback on it.
Definition
Event-driven architecture (EDA) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. An event can be defined as "a significant change in state"[1]. For example, when a consumer purchases a car, the car's state changes from "for sale" to "sold". A car dealer's system architecture may treat this state change as an event to be produced, published, detected and consumed by various applications within the architecture." [2].
