Couldn't agree more.
In the past, quota limits were based on 2 conflicting objectives: * discouraging people from building non-scalable applications by restricting APIs & time limits. * discouraging people from using app engine at an "unfair" cost during the request pricing regime. Except Google has straight up told me some of the issues I'm hitting are the result of a 3rd conflict. Not allowing you to build a Denial of service platform. (I am not allowed to work with 3rd party API's at rate greater than Google will allow) I agree by default you shouldn't be able to build a DoS platform, but you should be able to get the training wheels to come off, and not have them randomly comeback, or be able to get them removed when you need in a reasonable amount of time. My issues are much more simple: That support sucks. That changes are made without documentation. Seriously. Anyone want to raise their hand and tell me how great the support is? Or how it got better when it moved to Stack Overflow? Support is primarily outsourced. You hope the community can help with your issue. From this thread you can tell how well that works. The community can't fix a down instance, or that you are locked out of pushing versions because they had a glitch during your upload and appcfg thinks you are in more than one upload. Which usually happens when something is broken, and you might need to push a new version. The community can't fix that Memcache is slow, or that for some reason your datastore is in read only mode. Everyone on this list had experienced the joys of this kind of thing. Most people end up on this list because they experienced this kind of thing, and it was their first introduction to the group. Anyone want to raise their hand and say, "Yeah I get notifications when they change how the request scheduler works, Google is so great about telling me about tweaks, that just before they do a push I update my min-max idle thread and my pending latency settings". I didn't think so. Edgecache how many support threads are there in this group because EdgeCache changed its behavior? AppsForDomains Policy changes. "we added a new word to our list of words you can't have in your domain, Fart is now included, So SFARTInstitute.com is down" AwesomeSauce. None of those issues are Python, Go, or Java. None of those issues are "this one feature I was using broke". These are inherent in the way Google has chosen to do business. That they have picked a modus operandi that is not compatible with enterprise scale applications. -- 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.
