Document Extract
The concept of an Event Driven Architecture (EDA) has recently been the subject of some controversy when considered in the context of the general adoption of Service Oriented Architecture (SOA). In particular, there has been a high degree of confusion around whether the two architectures are compatible or competing and whether EDA combined with SOA forms what some analysts have referred to as SOA 2.0. Dispelling this confusion, it becomes clear that the term EDA is being used in three different ways within the SOA context. Associated with each of these is potentially significant, but different, value for any organisation grappling with SOA deployment. The most significant in terms of long term benefit is the application of EDA to the problem of control of the deployed SOA network through Management by Exception.
Unsurprisingly, the diverse interpretations of EDA makes understanding of vendor strategies and product strategies difficult. To address this specific challenge, this Lustratus Insight also compares the strategies of the vendors with EDA products in the context of these three interpretations.
|