I don't see this getting that much traction. Most existing PHP code is heavily dedicated to the use of SQL, and if you don't use the key-value datastore you giv

I don't see this getting that much traction. Most existing PHP code is heavily dedicated to the use of SQL, and if you don't use the key-value datastore you give up a lot of the scaling advantages of appengine. Secondly, PHP devs and sites are used to very affordable hosting options, and GAE is horribly overpriced for the computing power you get. Thirdly, Google doesn't really seem to care about customers of their AppEngine platform. App Engine Java routinely routes clients to new VMs that are not finished starting up, giving clients 5-15 sec delays on page loads. Google's response to this was to give a lecture at I/O 2013 on how to hard code configurations into your java code [1]. Basically, if you thought Heroku did a poor job of load balancing, Google App Engine takes the cake for terrible load balancing. I really don't know who Google is trying to target with GAE - they seem to be trying to cater to bloggers, small startups, and enterprise all at once. This pretty much just gives everyone the worst of all worlds with bloggers getting a system that is very complex, small startups getting excessive costs as soon as any processing is involved, and enterprise getting a system that will likely fall out from under them in 5-10 years time. [1] https://groups.google.com/forum/?hl=en&fromgroups#!topic/google-appengine/Nz4Yt8V6PB0 https://groups.google.com/forum/?hl=en&fromgroups#!topic...