My company went into production with DynamoDB and the provisioning 
throughput issues and cost became a major issue for us. We ended up 
achieving far better results and incredible cost savings by rolling our own 
using Amazon S3 for a datastore.

You can read the case study here: http://www.s3nosql.com


On Wednesday, January 18, 2012 2:57:10 PM UTC-5, Brandon Wirtz wrote:
>
> Google should pay me to do a parody of this 
> http://www.youtube.com/watch?feature=player_embedded&v=oz-7wJJ9HZ0#!
>
> I might do it for free, but I suspect the audience for such a video is 
> somewhat limited.
>
>  
>
> Dynamo Misses the Dynamic portion.  Turn the dial to determine how many 
> queries per second you need to serve from this non-relational Database. Got 
> a Traffic Spike? Sucks to be you. Oh, they failed to mention, “changing the 
> dial on a 100gig database?”  it requires “about 1.5 minutes per gig when 
> scaling up”.  So those of you with 4TB of data, if you want to scale up 
> you need to give them 4 days notice.
>
>  
>
>  
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to