• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (3)

1 localhost commented Permalink

If you want to study simplicity (a good thing, IMO), I'd suggest looking at it from an architectural POV rather than a, erm, non-architectural POV. REST kicks WS-Butt on simplicity because it adopts constraints which provide it. You don't get anything for free; entropy sucks.Asking "Do you prefer ..." is the wrong question. The right question is "What degree of which architectural properties do I require to meet the requirements of the project".Also, "Do you want to support one set of XML data formats (SOAP/WSDL) or potentially negotiate the data format every time (REST)?" draws a false dichotomy, since that isn't the choice to be made. In fact, for data formats, both architectural styles are pretty much even since neither places any extreme constraints on them (though REST's self-descriptive constraint does, it rarely impacts data format design in practice IME).

2 localhost commented Permalink

I speak from the perspective of someone who actually develops web services all the time, and I've been to both places. Just like the other comment mentioned, it's wrong to ask which one is simpler without an application context. What do you want to achieve? What's the scale of the project? What is the reusability requirement?

 
So far, all my projects (ranging from small to big) are telling me that REST is far simpler than SOAP, both for the service developer and the service user. Maybe there are specific projects for which SOAP is indeed better, I just haven't seen one.
 
Search on the web and check for yourself which approach is gaining momentum in the user community. I heard of a very good quote somewhere:"If you need consultants to tell you that something is better than the other, then most likely it is not.". Follow the user.

3 localhost commented Permalink

Saying REST leads to "a lot of litle URLs" is nonsense. To make a URL more coarse grained, you simply parameterize it, as in: http://example.com/getProduct?id=12345. The author's point about there being only four operations is similarly uninformed. Anything he can do in SOAP/WSDL, I can do in REST, and my code will be smaller, faster, more reliable, and more secure. The only problem with REST is that IBM can't make money off it.

Add a Comment Add a Comment