Here's my thoughts on the matter, as posted a few weeks ago http://joerussbowman.tumblr.com/post/182818817/why-im-dropping-google-appengine-for-my-primary
Basically, it depends on whether or not appengine is the right tool for the job. If you have a lot of reading/writing to backend datastore, such as in the case of http sessions, then I'd probably not recommend it. I believe a higher profile app will see less errors due to it being kept hot most of the time, however for low use apps that will see more cold boots on requests, you really have to be careful. I will say, since whatever fix happened for the imports issue, I've seen a little more reliability from my apps, but, it's not been long enough (or used enough) for me to really stand behind that feeling. My app, django using appengine-patch and gaeutilities session, was seeing enough problems that even I stopped using it, and have since decided to move off of Appengine for that specific project. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
