Here are some other (time wasting) questions to answer:

* What is a message?
* What is data?
* What is metadata?
* What is the difference between EAI and ESB? (watch out, this one is a flame troll)

The answer is: who cares! Does it matter how a Service is defined? If anything, it matters more about how to implement the *right* kind of Services than make one feel better about whether or not one has one ;) Getting the answer to "what" is a Service or application right is not important. Getting the answer as to HOW to do Service-orientation right makes a world of difference.

Yes, this is a flame troll ;)

Best,
Ron

Jan Algermissen wrote:

>> Some of the definitions I've come across for a Service are:


IMHO, substitutability (of one service by another) is an important 
concept. If you go to shoe order processor A and find it is down, you 
can equally well turn to shoe order processor B, given you know they 
are substitutable.

A real world example is that you can use another Web search engine if 
your favorite one is down, because you happen to know that they are 
both Web search engines.

HTH,


Jan






-- 
_____________________________________________________________
Ronald Schmelzer
[EMAIL PROTECTED]
Senior Analyst
ZapThink LLC
Direct: 781-577-2779 / Main: 781-207-0203


    


  

SPONSORED LINKS
Service-oriented architecture Computer monitoring software Free computer monitoring software


YAHOO! GROUPS LINKS




Reply via email to