OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-blueprints message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [soa-blueprints] Anti-Blueprints - Number of services

This conversation must be framed in a formal definition of SOA of
course.  Without such a definition, it could go around in circles.  I
have relied on the editors draft 10 of the SOA RM work.


-----Original Message-----
From: Duane Nickull [mailto:dnickull@adobe.com] 
Sent: Tuesday, November 01, 2005 7:25 AM
To: Davies Marc; Miko Matsumura; Jones, Steve G; Beack, Theo; Ken Laskey
Cc: soa-blueprints@lists.oasis-open.org
Subject: RE: [soa-blueprints] Anti-Blueprints - Number of services

-----Original Message-----
From: Davies Marc [mailto:Marc.Davies@uk.fujitsu.com] 

I think Duane's example of the Internet perfectly underscores this
- inasmuch as the Internet is a collection of millions of services - it
(IMHO) *not* an SOA - unless we're talking Service Oriented Anarchy :-)

... it doesn't conform to architectural disciplines, anyone can code how
they want, anyone can deploy what they want, there are no checks to
services deliver on their promised capability (I could go on). Sure, its
excellent example of how millions of services can be operating - but,
also an illustration of how millions can end up delivering very poor
service, to analogise - if you google the 'wrong' search string - you
end up
with 1 million 'hits' = meaningless.

Hmm - I strongly disagree with this assertion.  The internet has the
same patterns as web services.  Request-response is the primary
mechanism, returning either a success state or a possible error code.
It is message oriented and event driven.  Each service may have specific
policies, metadata (<meta> tags along with the search engines synopsis),
a contract for use (in most cases it is freely available to everyone who
asks) and there are multiple mechanisms for advertising the availability
of services.

One of the core tenets of interface based design is that anyone can
implement whatever they want behind the service interface.  It is not
limited to just coding either - you could deploy chimpanzees with
abacuses who then serialize a response back into html.  The point is
that the interface hides the implementation and insulates the consumer
from those details.  This is another of the core tenets of SOA.

Your claim that the internet delivers poor services is also
unquantifiable.  From a pragmatic architectural standpoint, the value of
the content is moot.  It is the architecture that is SOA, not the
usefulness of the content.

Google roughly equates to the concept of the advertising/discovery
mechanism in the SOA Reference Model.  Yes - getting hundreds or
thousands of results is sub-optimal, however the patterns are the same.

The internet is the single largest SOA on the planet.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]