We use it to power the Simple Database for QuickFuse: http://quickfuseapps.com http://quickfuseapps.com As some have mentioned here, there is a latency cost fo

We use it to power the Simple Database for QuickFuse: http://quickfuseapps.com http://quickfuseapps.com As some have mentioned here, there is a latency cost for every request, maybe around 200ms. So, we try to pack as much into each request as possible. QuickFuse is a voice app development environment. Since customers are using QuickFuse's Simple Database to store completely arbitrary, semi-table-structured data, SimpleDB was really one of the few choices we had for allowing this data storage to scale on the backend. One of our main requirements was that customers wouldn't need to specify the structure of their tables in advance, so most other databases weren't an option, except maybe Couch. What's perhaps more interesting, for anybody who's tried out QuickFuse, is that we wrap everything in both a nice GUI so people can upload "tables" of data and work with them, and also an API so data can be uploaded and downloaded programatically. Both the API and GUI make calls through our servers to SimpleDB.