What is Event Driven Architecture (EDA) and Why Does it Matter?
by K. Mani Chandy, CalTech, and Roy Schulte, Gartner Inc.
Event processing has emerged as one of the most important issues in IT today. Event processing encompasses two separate, although related, ideas:
1. Architecture: Event-Driven Architecture (EDA) is a style of application architecture centered on an asynchronous “push”- based communication model. EDA is the software architecture of choice for implementing “straight through” multistage business processes that deliver goods, services and information with minimum delay. Applications designed using EDA are also easier to modify than traditional applications as business requirements change.
2. Sense and Respond: The ability to respond rapidly and effectively to changing conditions is a powerful competitive advantage. Companies can use Complex-event Processing (CEP) techniques, a sophisticated form of EDA, to extract the information value from multiple events. CEP systems find patterns in event data to detect opportunities and threats. Timely alerts are then pushed to the appropriate recipients, often using Business Activity Monitoring (BAM) dashboards or similar end-user information delivery channels. The result is faster and better operational decisions and more timely responses to important situations. Download-PDF
- July 17th, 2007
2 Responses to “What is Event Driven Architecture (EDA) and Why Does it Matter?”
Leave a Reply
You must be logged in to post a comment.
Decision management is critical to event driven architecture…
I saw this article What is Event Driven Architecture (EDA) and Why Does it Matter? over on Complex Event Processing. It’s a great overview of what it means to have an event driven architecture. It talks about EDA combining an……
[...] 3. There was very little mention of EDA and events from any of the BPM experts present. The roundtable format meant that there were plenty of interesting discussions going on, but you only got to hear some of them – so perhaps event-processing came up in some other sessions. There was, though, some mention of the BPM-SOA boundaries. [...]