AUTHOR: http://aws.typepad.com/aws/2005/09/rest_vs_soap.html LINK!

Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Scoble goes to Amazon and Learns All About Web Services & Developer Contest | Main | SMS is SMileS Better »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef00d83425643853ef

Listed below are links to weblogs that reference REST vs SOAP:

» REST misunderstandings from AsynchronousBlog
It's really unfortunate that the REST community has mis-represented REST so thoroughly. Mark Baker points to an excellent example, and I offer another: Amazon Web Services talking about SOAP vs. REST. It's quite unfortunate when one of the largest "RES... [Read More]

» REST misunderstandings from AsynchronousBlog
It's really unfortunate that the REST community has mis-represented REST so thoroughly. Mark Baker points to an excellent example, and I offer another: Amazon Web Services talking about SOAP vs. REST. It's quite unfortunate when one of the largest "RES... [Read More]

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

pwb

People always seem to write that REST is so much easier and works fine but that SOAP is good for some things but then never point out what these things are. REST seems to work fine for the vast, vast majority of what people are doing so why do I wnat to use SOAP?

William Drury

Same here. I have been parsing XML feeds from Amazon, SearchFeed, Gigablast, Google, FindWhat and many others for years, and in every case, REST was the way to do it. In fact, I had to look the acronym up, I was just calling it 'XML over HTTP'.

Granted, the Amazon feed is highly nested, highly variable, and can follow a number of different formats (even more, now that we can request Response Groups). Generally, this is the most complicated piece of the equation, and can be a frustrating, error-prone experience to parse correctly. But 4.0 has been out long enough that API modules like PERL's Net::Amazon and others should hide most of that complexity.

We're already using HTTP to deliver the results as HTML, why add another layer of complexity? REST works.

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30