I've seen apps sustain around 800 QPS for 12 or 13 hours with little issue. There are a lot more issues that start to bite you as your QPS increases, both on the front-end and back-end processing. It is important to have a well thought-out design. If your app is able to return _very_ fast from most requests, GAE is an OK choice.
You would definitely need to work with the GAE team to get many quotas and limits significantly increased for your application. There are a lot of backend per-minute limits that a lot of people probably never need to think about. Robert On Fri, Feb 18, 2011 at 15:53, Pancho <[email protected]> wrote: > Hello, > > Assume that a couple of years ago Twitter would have been developed on > GAE. > > would it have scaled to the current number of users and traffic. > > Thanks. > > -- > 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. > > -- 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.
