- "Also remember a GAE instance allows you to handle exactly one request at a time." It is not true for JVM application instance - it handles requests concurrently.
Besides, GAE memcache is globally visible to all instances, but in AWS you need to setup your own per instance or 3rd party thru REST. If you have 8 instances up, then you'll have to have 8x more memory for your caching - separate record for each instance. Plus, with global cache, you may store temporary flags/signals/locks etc. Memcache requests will be faster inside GAE than to 3rd party. On May 31, 9:10 am, "Raymond C." <[email protected]> wrote: > By "GAE provides you much more", you mean much more *limitation* right? > > The cost on setup is trivial for a long run application when compared to the > hosting cost. I dont think the high price worth that cost for long term. > > Also remember a GAE instance allows you to handle exactly one request at a > time. The cost is not just 4X or 8X, but 40X or 80X if one instance on EC2 > can handle 10 requests at a time, which is normally much higher than this > number. -- 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.
