Service Characteristics
- A "simple" server or service produces exactly one
output per request: e.g. a stock quote server.
A "persistent" server or service may produce multiple
outputs per request: e.g., an RSS server.
For many services, we assume they behave like a mathematical
function: if we know the request inputs, we can predict the output.
E.g. if we know the postscript file, we know what the printer will
print.
"Afunctional" servers and services behave more like a
black box from the standpoint of the client. E.g., when one calls a
web server with a URL, one does not know the current state of the web
page, or even if one will be returned.
The agreement between the server and client need not be
explicit. There may be expectations based upon assumptions and or
there may be an explicit description of the service.
The request consists of some kind of communication signal, such
as the wave of a hand, and may be ongoing, such as a
subscription.
We now describe how CIT services are used within an SOA motivating
formal descriptions of such services consistent with these
informal ones.
©2012
Charles Petrie - permission to reproduce widely with attribution.