I still think we should distinguish between SOA (service oriented architecture) and WSA (web services architecture). While WSA and REST are competing architecture styles, SOA (at least as I and most people I talk to understand this term) is higher level. Services in SOA have descriptions, they are visible in some sort of registry, they have consumers using services under some contracts, they have lifecycle... there is no REST vs WSDL debate on this level.

Radovan

On 3/17/06, Mark Baker <[EMAIL PROTECTED]> wrote:
Hi Eric,


On 3/16/06, Eric Newcomer <[EMAIL PROTECTED]> wrote:
> hi Mark,
>
> It is strange how closely we can almost agree on
> things most of the time ;-)

Strange indeed! 8-)


> I do not agree with your opinion that the Web and Web
> services are competing architectures, however.

To clarify, I mean competing in the sense that for a given problem
that needs an automated solution, each architectural style would
suggest a different solution (or set thereof).

I know you've always felt that there's little (significant) overlap
between the problems that a RESTful solution is suitable for, and the
problems for which an SOA solution is suitable for.  But my
experiences - which includes both large scale CORBA and Web projects -
suggests considerable overlap.  In fact, reflecting back on my largest
CORBA project - a telecom SONET service management system which
integrated billing, network management, provisioning, and workforce
dispatch, and for which I was infrastructure team lead - the Web would
have provided a far superior infrastructure than CORBA (Orbix, in fact
- sorry! 8-).


Mark.
--
Mark Baker.  Ottawa, Ontario, CANADA.       http://www.markbaker.ca




SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS






--
Radovan Janecek
http://radovanjanecek.net/blog

SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to