1. If you always have only one request running at a time then 3 instances sounds bad indeed. 2. Backends are decent, but more expensive. You can probably get the same work done on a frontend instance, but cheaper. 3. Cron is unreliable, use the task queue instead.
On Apr 20, 10:00 pm, Ido Ran <[email protected]> wrote: > Hi, > I'm writing an application that read messages from twitter on GAE. The > application should read messages all the time and react to them. > Because I'm currently testing an idea I don't want to use backends, which > are the natural choice for such need. > I'm using a cron job that run every minute and servlet which handle the job > by running for as long as 50 seconds continually reading messages. > > 1. I've notice that GAE open up to 3 instances to handle only this trafic, > is that bad? > 2. Backends are the right tool for such job, right? > 3. Is there better way of doing it without backends? > > Thank you. -- 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.
