Event Driven Architectures
In the Gartner Submit of 2006 Mani Chandy talked about the existence of a misconception of Event Driven Architecture (EDA). So, he proposed to talk about the understanding of EDA and its Return of Investment. So he can evaluate the true costs and benefits. In this talk an event was defined as:
“An event is a significant change in state. I want to emphasize that an event deals with CHANGE.”
For example:
So, if the event is a change in the state. The Event Driven Architectures are a specification of an expectation of the state of the world. If in the model that the application tries to fit there are a lot of “normal” events. In general, normal types of events are already handled by the Service oriented application (SOA). In fact you can choose use soda if “If you are seeking to support strong cohesion in the business processes, situations where all process steps are under one control, SOA is the way to go” (How Eda Extends soa and why it is)
Taking these principal points into consideration. There are four points to fit an Event Drive Application:
- Sense and Respond Value Prop: Timely Response when reality deviates from expectation.
- Asynchrony: Timing of events are not controlled by the enterprise
- Global Situational awareness: by correlating multiple sources of data from outside the enterprise with enterprise data
- Errors: external data is more noisy.
Sources: