title: message driven vs. event driven approaches to application integration
body: <p>I was wondering if there is a clear distinction between message driven and event driven environments when we refer to SOA or middleware and generally in cases of application and enterprise integration. I understand that a user interface resembles an event driven model where our system intercepts action by the user.</p>
  
  <p>Also it is clear that messaging supports systems based on publish/subscribe, sychronous or asynchronous communication, transactions etc.</p>
  
  <p>But is there a difference in the middleware/soa/application intergration context? (architecture level). I am trying to consult sources such wikipedia (<a href="http://en.wikipedia.org/wiki/Message_Oriented_Middleware" rel="noreferrer">here</a>, and <a href="http://en.wikipedia.org/wiki/Event-driven_SOA" rel="noreferrer">here</a>), but I am still somewhat confused. When should a developer prefer one solution over the other?</p>
  
  <p>Are there examples or cases where one approach makes more sense than the other? Or any comprehensive resources and guides to implementing each one?</p>
  
  <p>Many thanks for any insight.</p>