On Wed, Jun 13, 2012 at 2:39 PM, alex <[email protected]> wrote: > > Secondly, for a mid to high load app you will definitely end up running more > than one EC2 instance (otherwise, you might as well deploy your app on a PC > sitting under your desk). If you don't setup Autoscale thing (if you do - > here's your billing going up already), sooner or later you'll have to do it > manually. Both ways, there will be additional costs. Not only that, you'll > also need to allocate some (human) resources to manage that little cluster > on which your app/whatever is running.
Replace "AWS" with "Elastic Beanstalk" in my comments and yes, it is very comparable with GAE. The real question is to what extent a performance degradation in the datastore (say, DynamoDB) will force an uptick in the # of appserver instances required. Non-GAE systems aren't very sensitive to this; doubling the latency of a datastore request may double the number of threads blocked on I/O in the appserver, but there should be plenty of headroom in any java appserver. Threads blocked on I/O are silly cheap these days. It's possible that Google can solve this problem entirely by getting better concurrency out of instances. Is there still a hard limit of 10 threads? Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
