 |
 |
 |
Perhaps like this:
The receipt of a message is a network level view of the
architecture. The receipt of the event type is the
enterprise level view.
The network sees a message. The enterprise sees the
content type the message wraps.
len
From: Chiusano Joseph [mailto:chiusano_joseph@b...]
> Are services responses to events?
I believe they are, though some consider this a
separate-but-related-to-SOA concept. I believe Gartner has a concept
called Event Driven Architectures (EDA), which - if I recall correctly
since reading up on it months ago - they consider as another
architectural style (i.e. apart from SOA), but related.
In essence, the invocation of a service is an event in and of itself -
for example, the receipt of a purchase order by a supplier that is using
Web Services in a SOA can trigger the processing of the purchase order
and (if all goes well) the creation and transmission of an invoice. So
the events here would be the receipt of the purchase order, the
validation of the purchase order, etc.
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |