A âtestableâ definition is indeed a worthy objective. The definitions
that I have gathered so far indicate that SOA is an application design
philosophy that is open to whatever interpretation suits your purpose.
For instance some of the smaller development companies that I have
spoken with insist that their deliverables are SOA because they have
implemented a few web service APIâs. No thought about autonomy,
boundaries, policy, contractâ¦. The big boys focus on SOA appears to be
around selling you an enterprise messaging system and little else.
Markâs approach as in how to âevaluate a system to determine whether
it's architecture is SOA or not, as well as understand what changes
I'd need to make for it to become SOA (including what advantages I'd
gain in doing so)â would seem to me to be quiet fundamental. In fact I
am struggling to understand the SOA hype without answers to such
questions.
Selwyn
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
