I think that GAE is not best solution for this kind of application. You are much better with dedicated / cloud instances and Cassandra (or other noSQL solution) to work around mysql scalability.
Maxim. On Fri, Jan 14, 2011 at 8:24 PM, supercobra <[email protected]> wrote: > Hello again, > > > > Again as Eli mentioned, to offer any solutions we'd need to know what > > you're trying to do in all those tasks. > > We are exploring the idea of migrating our website monitoring service > Montastic (www.montastic.com) to GAE. Right now it works on MySQL but > scalability becomes challenging and we need to explore a > re-architecture of our system. GAE would be ideal if it was possible. > So we do need to do a LOT of UrlFetch-es every 1, 2, 5 minutes. > > One of the challenge is to wait for 5 minutes. E.g. Fetch a URL, store > results, wait 5 min, do it again. Since a queue will execute the task > almost immediately (if it is empty) this would not work unless the > queue is filled w/ a known number of tasks. > > > Any suggestion welcome. > > > Daniel > > -- > 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]<google-appengine%[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.
