There has been several new mashups using the Amazon ECS recently.

Here are some of them (information from ProgrammableWeb):

• The Amazing Baconizer
  Connecting a million popular culture dots via the Amazon API. Describe two items and see how they’re linked by consumer preference via intermediate items. Choose from books, CDs, or films, and you can mix and match.
• ActorTracker
  ActorTracker takes feeds of upcoming television shows, movies and celebrity news combined into a shopping experience with merchandise from Amazon and eBay.
• AmazonHive
  Alternative interface into the Amazon catalog. Java applet with price sliders and other filtering tools.

I haven’t had much time yet, but will look into them over the next few weeks. You can view all mashups that utilize the Amazon API listed in the ProgrammableWeb database here.

For developers .NET developers, you can jump start mashup development with the AmazonCommerceService.NET by Ed Quinn. More information from a recent post by Jeff Barr…

“AmazonCommerceService.NET is a set of .NET classes. It creates REST requests for ECS and then queues them up, dispatching them to Amazon at the rate of 1 request per second per the license agreement. The results are delivered asychronously as they arrive, using a delegate. Batched requests are supported.”

The source code is C# and framework is .NET 2.0. Also, Microsoft users can get the AmazonCommerceService.NET MSDN Compiled Help. For more information see Jeff’s his full post.

The last good ASP.NET implementation I saw was in a web application called StorePerfect for ECS 3.0, a few years ago. I will report further on this one once I have loaded the sample up and given it a whirl. My question to Ed, and maybe this is silly, but why was REST was choosen over SOAP?

[tags]ASP.NET, mashups, Amazon, Amazon ECS, Amazon Web Services[/tags]