RE: Application design & architecture

midrange-l-request@xxxxxxxxxxxx wrote:

>   6. RE: Application design & architecture (Chris Payne)
>
>>From this point of view, as opposed to building my own atomic clock, I
>can just connect to a government time server and use NTP to get the
>time, and that is an example of SOA?

This is the kind of example that makes useful sense. Expanded upon and applied 
to an enterprise, it becomes a way to think of it somewhat like 
"Service-program Oriented Architecture". (Just for the sake of discussion...)

An enterprise may have numerous Divisions, some of which may be previously 
acquired companies in themselves. One Division might have an excellent facility 
for handling credit card numbers -- verification plus all kinds of added 
goodies. Why should every Division need to create their own credit card 
functions or even manage a copy? Advertise the Service via an Enterprise UDDI 
registry and access the one that already exists. In that sense, it can be 
viewed as a service program access over the inter(intra)net.

Some of the distaste _appears_ to come from the thoughts related to accessing 
services from other companies, but I haven't seen that as a requirement but 
merely a possibility. Yet, credit card verification might be a very good 
candidate for such a service between companies.

Tom Liotta