Re: Introducing the Service Oriented Architectural style, and it's constraints and properties.

Walden Mathews <[email protected]>
Newsgroups gmane.comp.web.services.ws-arch
Message-ID <004801c2d378$0a449c00$1702a8c0@WorkGroup>
> >  There
> > are limitations to HTTP that can be ameliorated by the use of SOAP.  In
> > cases of Service-oriented applications, such as messaging systems, it is
> > easier to build applications in an SOA style.
>
> I have to disagree there.  I've yet to see a SOA app that wasn't far
> simpler to develop than a REST based app.

Did you mean "more complex"?  And yet it's claimed that REST style,
while not necessarily easy, has longer term payoffs.  Can we come up with
a consistent analysis of SOA vs REST, simple vs complex, easy vs hard,
short-term vs long-term?  Or else maybe just drop the analysis from the
proposed text?

Walden
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.