You have to spend more time trying to get around all those random quota and rate-limit landmines than you spend actually developing your application. Then you have to deal with having your processes killed all the time for bogus reasons. So this is not ready for business yet. If my app is working before Google gets this stuff working, I will have no choice but to find another host.
I think calling it a joke is too harsh, though. They make it clear that this is a "preview release" which means "not even beta" in my mind. If they still have these limitations when it comes out of beta, you can call it a joke. Calling this "cloud computing" is a bit of a joke, though. Cloud computing means you get more if you pay more. But on appengine, you can pay all you want yet you'll still have 30s execution limits, 1M taskqueue limits, 1MB URLFetch limits, simultaneous access limits, 10 fetches per second (no matter how many users) limits, etc. etc. etc.. This isn't cloud computing unless they let our apps scale with our bank accounts. But still, I'll stick with Google in hopes that their hosting is ready for the prime-time before my app is ready for the prime-time.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
