Matches in DBpedia 2014 for { <http://dbpedia.org/resource/Event-driven_architecture> ?p ?o. }
Showing items 1 to 30 of
30
with 100 items per page.
- Event-driven_architecture abstract "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". 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 whose occurrence can be made known to other applications within the architecture. From a formal perspective, what is produced, published, propagated, detected or consumed is a (typically asynchronous) message called the event notification, and not the event itself, which is the state change that triggered the message emission. Events do not travel, they just occur. However, the term event is often used metonymically to denote the notification message itself, which may lead to some confusion.This architectural pattern may be applied by the design and implementation of applications and systems which transmit events among loosely coupled software components and services. An event-driven system typically consists of event emitters (or agents) and event consumers (or sinks). 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. The first category of sinks can be based upon traditional components such as message-oriented middleware while the second category of sinks (self-contained online reaction) might require a more appropriate transactional executive framework[clarify].Building applications and systems around an event-driven architecture allows these applications and systems to be constructed in a manner that facilitates more responsiveness, because event-driven systems are, by design, more normalized to unpredictable and asynchronous environments.Event-driven architecture can complement service-oriented architecture (SOA) because services can be activated by triggers fired on incoming events.This paradigm is particularly useful whenever the sink does not provide any self-contained executive[clarify].SOA 2.0 evolves the implications SOA and EDA architectures provide to a richer, more robust level by leveraging previously unknown causal relationships to form a new event pattern. This new business intelligence pattern triggers further autonomous human or automated processing that adds exponential value to the enterprise by injecting value-added information into the recognized pattern which could not have been achieved previously.Computing machinery and sensing devices (like sensors, actuators, controllers) can detect state changes of objects or conditions and create events which can then be processed by a service or system. Event triggers are conditions that result in the creation of an event .[citation needed]".
- Event-driven_architecture wikiPageExternalLink Event-Driven%20Applications%20-%20Costs,%20Benefits%20and%20Design%20Approaches.pdf.
- Event-driven_architecture wikiPageExternalLink 1816129.htm.
- Event-driven_architecture wikiPageExternalLink how-eda-extends-soa-and-why-it-is.html.
- Event-driven_architecture wikiPageExternalLink www.complexevents.com.
- Event-driven_architecture wikiPageExternalLink 5th-anniversary-edition-event-driven-architecture-overview.
- Event-driven_architecture wikiPageExternalLink www.ep-ts.com.
- Event-driven_architecture wikiPageExternalLink soa-eda-and-cep-a-winning-combo.
- Event-driven_architecture wikiPageID "4731786".
- Event-driven_architecture wikiPageRevisionID "602726132".
- Event-driven_architecture hasPhotoCollection Event-driven_architecture.
- Event-driven_architecture subject Category:Enterprise_application_integration.
- Event-driven_architecture subject Category:Events_(computing).
- Event-driven_architecture subject Category:Service-oriented_(business_computing).
- Event-driven_architecture subject Category:Software_architecture.
- Event-driven_architecture comment "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". 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 whose occurrence can be made known to other applications within the architecture.".
- Event-driven_architecture label "Architecture orientée évènements".
- Event-driven_architecture label "Arquitectura dirigida por eventos".
- Event-driven_architecture label "Ereignisgesteuerte Architektur".
- Event-driven_architecture label "Event-driven architecture".
- Event-driven_architecture label "Событийно-ориентированная архитектура".
- Event-driven_architecture sameAs Událostmi_řízená_architektura.
- Event-driven_architecture sameAs Ereignisgesteuerte_Architektur.
- Event-driven_architecture sameAs Arquitectura_dirigida_por_eventos.
- Event-driven_architecture sameAs Architecture_orientée_évènements.
- Event-driven_architecture sameAs m.0ckfb2.
- Event-driven_architecture sameAs Q991296.
- Event-driven_architecture sameAs Q991296.
- Event-driven_architecture wasDerivedFrom Event-driven_architecture?oldid=602726132.
- Event-driven_architecture isPrimaryTopicOf Event-driven_architecture.