The main benefit of say Heroku is that while migrating away is not trivial, in principle you shouldn't have to rearchitect your app to do it.
I kinda like Datastore though. Maybe I'm just use to it. The limitations just make sense if you want to scale.
They also have a RDBS you can use though ... I've never used it.
Still haven't figured out a clean way to do geospatial stuff with Datastore, so that is one big caveat.
How is that an advantage over App Engine, given the existence of AppScale? [1]
[1] http://googlecloudplatform.blogspot.com/2013/09/appscale-bri...
We aren't live yet, so I haven't needed to think about that stuff yet. However, I've talked to people that have applications live on App Engine, and that hasn't come up in conversations ... so there must be some solution ... if not the exact one you want.
The vast majority of our traffic is from devices that retry later if anything goes wrong. It is analytics information and hence there is no human affected by it.
Despite having identical settings and code across a number of appengine apps, we see variance in the number of instances they decide to run (eg they will start 4 at once even though only 1 is needed for the load).
At one point they were starting hundreds of instances due to some of our aggressive inter-app traffic (thundering herd problem). Things would have worked fine if we could limit the number of instances, but tough luck there. It required considerable engineering and tuning to make the problem go away that would have trivially been solved (in the short/medium term) by limiting instance numbers.
Also, with managed VMs you can basically run anything you want and still get Google to manage things for you. Manage VMs give you a sort of script you can define that apt-get installs the packages you need. You can also use Docker if you like to make your own VM images.
Haven't used it yet, but it looks good based on the demos. They showed a demo with Node.js today.
While no longer necessary because of managed VMs, it would be very good to have Ruby support also. I tried JRuby and Sinatra on AppEngine many years ago but the long loading request times were a killer. Plain Ruby and Sinatra would be good.
For my part, I was more worried about not being able to execute 3rd party modules that aren't supported on App Engine ... but even that apprehension disappeared with today's announcement of managed VMs.
App Engine is a no brainer for me now. The amount I save on not needing an ops team for a long long time overcomes any slight misgivings that Google might abolish App Engine in a few years. I don't think App Engine is going anywhere, BTW. You look at the number of languages they are adding, the number of people they are hiring ... to compare that to Google Reader is a bit ridiculous.