$1226.4 is if you're hammering the data-base with intense queries 100% of the time (so it's always being utilised).
In reality (though this depends on how efficient their database is) it'll likely be orders of magnitude smaller.
I guess we won't know the costs in reality until the service is up. It pretty much all depends on how efficient their implementation is.
If a query takes 1ms, you're going to pay for one sixty-thousanth of $0.14 . I fail to see what you're doing? Or am I missing something?
but it could end up really expensive if you are hitting your database a lot. 100k users hitting a 2 second query per view ain't going to be cheap.
Machine Utilization - $0.14 per Amazon SimpleDB Machine Hour consumed
Amazon SimpleDB measures the machine utilization of each request and charges based on the amount of machine capacity used to complete the particular request (QUERY, GET, PUT, etc.), normalized to the hourly capacity of a circa 2007 1.7 GHz Xeon processor.
From here: http://www.amazon.com/gp/browse.html?node=342335011
does anyone know if this works like ec2 or not when it comes to hourly charging?
I love the idea but I feel the pricing should of been like s3 I.E just paying for storage and bandwidth.
I can't see how you would get out a key from the system when you add a new record...