Don't Forget: You Can Use Amazon SimpleDB For Free
aws.typepad.com
aws.typepad.com
There are too many limitations which makes SimpleDb almost impossible to use for complex data storage. A few examples of annoying limitations:
1. SimpleDb is a Key to list value pair storage engine (e.g. Key = Name, Values = [John, George, Ringo, Paul]). Seems good but you can only have 256 values per record.
2. Each value is limited to 1024 characters (512 for double byte)
3. Where clauses of "select" statements are ordered by their ascii values. Makes things relatively complex numeric values. Here's some suggestions from amazon when working with numerical values.
http://docs.amazonwebservices.com/AmazonSimpleDB/2007-11-07/...
and floating points are especially annoying:
http://stackoverflow.com/questions/691778/best-way-to-format...
Bottom line, my take is if you want to use SimpleDb for simple data storage, it's a wonderful service and relatively cost effective. If you're data is or will become complex then it's not the service for you. I'd look into Google App Engine for a robust and "free" service.
While 3. is a pain-point in many systems, the fact that you can do selects with where clauses on a key-value store that scales horizontally is impressive. The indexing they do can be very helpful in certain implementations.
Anyway I think 10gb per domain is reasonable for many people, but it is another limit of the store that could cause problems. Fortunately Amazon knows the boundaries of SDB, so it can put these in place and help inform decisions about using it for, say, a project that will need more than 10gb per domain, or more than 100 domains.
In terms of price, after the free quota is surpassed, does SimpleDB make sense for relatively small sites? i.e. sites with fewer than 200k uniques / month
It seems like you are referring to using it as a cache only, and on those terms, it really depends on your traffic profile. Chances are, though, with 200k uniques you would be pleased. If you are running in EC2, the bandwidth is free, so you only pay for computation. That can keep things pretty inexpensive.
100Hectares.com displays listings to cover the full range of Property needs, from buying, selling and renting to decorating, building; moving and financing, 100Hectares.com is an exhaustive resource for the entire Home and Garden industry. 100Hectares.com nice market position and expertise in Internet transactions, enables it to attract the highest level of relevant users looking for products and services in property sector. Providing a cutting-edge Internet matching and information service that brings together the best companies and the most informed consumers, 100Hectares.com is one of the best site serving an exclusive community, aiming to bring specialist, high quality companies together with Indian consumers in the most user friendly and efficient interaction possible. At our core is a team of professionals that value its clients, and our strong commitment to customer privacy is a key element of our success amongst users. 100Hectares.com has a strong and successful relationship with some of the top companies and suppliers in its relevant areas. This allows us to make thousands of quality offers available to the tens of thousands of relevant visitors every month.
You would have to ask each new user to create an AWS account (also free) and then enter their credentials (public key and private key). If you are building a browser-based app you need to protect the credentials from prying eyes/code.
Isn't this the problem that oauth is intended to solve?
[Edit] Now that I am having a little coffee, I realize that you would have difficulty knowing what the keys are to the queued messages. I guess you could use a set of known keys, and cycle through them looking for messages, but why be a cheapskate.