[
Lists Home |
Date Index |
Thread Index
]
Are services responses to events?
That is likely at least one level higher
in the organizational architecture if call
and response is the lowest level of description,
but if we are to speak of a 'services oriented
architecture' that is meaningful beyond the
most primitive descriptions, it can be useful
to think in terms of event types over
messages. Otherwise, a service and a method
are indistinguishable. I'm not sure the fact
of using XML to send and return the request or
the opacity at the boundary are enough to
distinguish a service from a method invocation,
remote or otherwise.
len
From: Michael Champion [mailto:michaelc.champion@gmail.com]
For what it's worth, all these discussions beg the question of what a
"service" is. I've taken a stab at this in
http://www.cioupdate.com/trends/article.php/3434691
'In the real world, we use services all the time -- getting money from
banks, ordering food from a restaurant, getting clothes dry cleaned,
and so on. What makes these "services" is that we don't need to know
anything about banking, cooking, cleaning, etc. in order to use them,
we simply request them.
...In a nutshell, service orientation is an approach to designing
systems in which each component knows only how to request and consume
the services provided by other components, and little about their
internal algorithms, data structures, stored data formats, query
languages, etc.
|
