IBM®
Skip to main content
    Country/region [select]      Terms of use
 
 
    
     Home      Products      Services & solutions      Support & downloads      My account     
 
developerworks > Dashboard > Bobby Woolf: WebSphere SOA and J2EE in Practice > Miscellaneous Technologies > Event-Driven Architecture
developerWorks
Log In   View a printable version of the current page.
Overview Spaces Forums Blogs Podcasts Wikis Exchange
Event-Driven Architecture
Added by bwoolf, last edited by bwoolf on Oct 17, 2006  (view change)
Labels: 
(None)

Event-Driven Architecture (EDA)

There's a (relatively) new buzzword (buzzphrase?) gaining popularity, Event-Driven Architecture (EDA).

EDA is a technique for integrating applications where an emitter posts an announcement of an event and handlers receive notification of it. The announcements are transmitted as event messages. Often the event messages are transmitted using one or more publish/subscribe channels--where handlers register interest by subscribing to a topic, and emitters announce an event by publishing to the topic--but that's not a requirement. A topic can have multiple event handlers subscribed, but could have none at all. Once a handler receives notification, it reacts accordingly, perhaps by doing nothing. An event processing network is a more sophisticated connection between emitters and handlers, which performs mediation for event messages.

What are some examples of how to use an EDA?

An obvious question is: How does EDA relate to SOA and ESBs?

I also discuss EDA in developerWorks Interview with Bobby Woolf.

For more info:

Docs EDA and SOA (Bobby Woolf: WebSphere SOA and J2EE in Practice)
Docs Event Driven Architecture Examples (Bobby Woolf: WebSphere SOA and J2EE in Practice)

Hi Bobby, I did some "popular"writing on EDA and SOA in a blog I recently started. You might find it interesting. http://soa-eda.blogspot.com

Posted by jack541108 at Aug 18, 2006 10:29 | Permalink

    About IBM Privacy Contact