The comment from Dave Peck on that post is interesting as well:
This is quite interesting, thank you. As someone who has worked with and on App Engine since the early days (I gave a talk at Google I|O 2009 about scaling with GAE) I agree for the most part with your final conclusion: “no system that is likely to become product ionized at scale should be written on App Engine.” This is a sad conclusion to arrive at after all these years, especially when the original promise of App Engine was (essentially) “write your applications against our strange, quirky API, and they’ll scale far more cheaply and reliably than they could otherwise.” I think the pricing changes, coupled with regular performance problems, gives the lie to that promise. I’m porting several of my apps off of App Engine, including a big production app (https://www.getcloak.com/) — luckily, the only “odd” service I make use of is the Task Queue. (Specifically, I make use of Task Queue transactionality — so there isn’t a direct analog in, say, Celery.) GetCloak.com is heading to AWS as well. http://www.vijayp.ca/blog/?p=162#comment-761 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/B-Ns5IJnIpEJ. 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.
