Amazon Web Services Blog: REST vs. SOAP

Web Services Wish List

Amazon E-Commerce Service (ECS) exposes Amazon's product data and e-commerce functionality.

Amazon Elastic Compute Cloud is a web service that provides resizable compute capacity in the cloud.

The Amazon Historical Pricing web service gives developers programmatic access to over three years of actual sales data for books, music, videos, and DVDs.

Mechanical Turk

One of the best ways to understand Amazon Mechanical Turk is to complete a HIT and see what the experience is like.

Simple Storage Service

Amazon S3 is storage for the Internet. It is designed to make web-scale computing easier for developers.

Simple Queue Service

Amazon Simple Queue Service offers a reliable, highly scalable hosted queue for storing messages as they travel between computers.

Alexa Thumbnails

All thumbnail images are accessible via web services, using SOAP or REST.

Alexa Top Sites

The Alexa Top Sites web service provides ranked lists of the top sites on the Internet.

Alexa Web Information Service

The Alexa Web Information Service makes Alexa's vast repository of information about the traffic and structure of the web available to developers.

Alexa Web Search

The Alexa Web Search web service offers programmatic access to Alexa's web search engine.

« Ask For Cents : New Mechanical Turk Application | Main | New Ways to Look at XSLT »

REST vs. SOAP

Kevin Daily offers a brief thought on REST vs. SOAP in the case of the Amazon Web Services.

We are still seeing an 80% REST / 20% SOAP usage pattern. Kevin correctly notes that the ease with which developers can invoke an XSLT transformation as the concluding step in a REST request makes for easier and simpler web development.

-- Jeff;

February 13, 2006 in Thought Pieces | Permalink

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/t/trackback/183837/4255410

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

» SOAP vs. REST from John Keyes
Great little summary of the old SOAP vs. REST question, from Don Box. Decide which to support based on your target audience. When I develop in PHP, I prefer REST, but when I'm in Microsoft's Visual C# environment, SOAP is... [Read More]

Comments

I completely agree.

The XSLT piece is the tipping point because then you don't really have to worry about parsing any troublesome XML, or dealing with an XSLT library/engine on your own.

I use REST/XSLT for my two main amazon tools that I wrote.

Simple and easy!

Posted by: Pat Rock | February 13, 2006 at 05:33 PM

ill have to investigate this rest,didnt realise that there was such a high usage of it