No, it's the worse PAAS in existence. Horrible proprietary NoSQL DB, filtered headers, must perform http requests with custom SDK (horrible SDK BTW...). It is absolutely not worth it.
The new Google "managed VMs" or whatever are closer to what Appengine should have been all along.
I'm not saying AWS is great, it has a horrible UI, but AWS has none of these silly limitations.
First, why do you think Google Datastore is any more or less proprietary than AWS Dynamo? (Which has its own eccentricities- like having to forecast and/or overallocate capacity in advance; while with Datastore you only pay for actual usage?)
Oh; and you can also use Cloud SQL or BigTable from within AppEngine.
> must perform http requests with custom SDK
What do you mean?
I can't imagine anyone reading HN who'd think this is the right solution in 2016. Even if you want to jump on the Google train (there are valid reasons for this, including free outbound bandwidth to YouTube and Google Drive...), there's no excuse for App Engine. Use the other Google cloud offerings. The container stuff is top notch.
And AppEngine is absolutely the right solution for some users, like people who don't want anything to do with sysadmin work, configuring containers, etc. (Like myself.)
I hear you about the pricing change. We talk a lot about not getting pricing wrong internally (now), as that's exactly what happened. Initial trial pricing is ... dangerous.
Disclosure: I work on Compute Engine.
The filtered headers thing is a common issue in many https load balancers, particularly ones like ours that have global anycast routing.
I've shown a bunch of people that a modern App Engine standard environment app can run stock Django talking to MySQL (which we manage for you with Cloud SQL) just fine. If you need native C-code extensions, sure use our new Flexible Environment (neé Managed VMs) but you don't need to for many simple apps.
Finally, as others have pointed out, App Engine is just one piece of our overall platform (though it was first, so it's common to have this misperception).
Disclosure: I work at Google on Compute Engine (so of course I want you to use our products).
I don't think so. A good while ago GAE was incredibly limiting - it certainly was when I tried it. Python only (maybe also PHP?), forced to use Google Cloud whatever for storage, etc. By comparison, AWS was using MySQL databases and EC2 boxes that let you use whatever language you wanted.
I know things have come a long way since then, but the reputation persists.
They now support Python, PHP, Java, Go.
And in beta, "flexible environment", which is like elastic beanstalk but more sensible: Python, Java, Go, Node.js, Ruby, <random docker images>.
Java here is a pure marketing effort to convince a clueless manager saying hey we got java!
What if there exist Java-based system that somehow can be deployed to GAE with minimum changes...? (e.g.: not needing itext)
What if there exist a company that the majority of developers prefer Java?
I think the order in which GAE added languages was Python, Java, Go, PHP.
But heh! You do you, I'll keep my platform agnostic config management thank you very much. Life's too short to be beholden to any one vendor.
You can downgrade to manally managed servers with the the same codebase.
Or you spend the few extra hours upfront wrapping your app in config management so it can run on any bare VM.
Don't be lazy! Not being able to run anywhere is technical debt. Unless you're running a hobby site that generates no revenue; in that case, do whatever.
After revisiting it the past year.. I don't really understand why the in comparison pathetic AWS Lambda gets so much more attention, for instance.
There is this: https://www.appscale.com/
It's an open source implementation of the App Engine APIs. The website doesn't make it very clear but the source is on Github: https://github.com/AppScale/appscale
Last summer I switched jobs from a company where we developed loads of cloud thingies ourselves, because there really weren't any good options around ten years ago when we started a product line that needed a high quality global service (involving processing, networking and storage). We had a lot of fun basically building our own little (if 5000+ machines qualifies as little) AWS/Google-style Cloud. I heard about Amazon Dynamo in 2007 and then we basically re-implemented it ourselves. We added lots of neat features like datacenter-aware global replication, etc.
When I joined the new company last June, it was basically just me. A few months later we hired a great python dev. I'm so happy to find that the level of the openly available products/services had caught up quite a bit by then, enabling us not to spend so much time on just making sure things were available all of the time, and ~infinitely scalable.
I spent a lot of time evaluating AWS vs GC, but my inevitable conclusion was that.. in a small company where you don't want to invest in a 24/7/365 devops team you should go for the Google App Engine.
I would really like it if Google found some pragmatic way to make App Engine work inside China though, at least for companies that have chinese ICP permits.
(Why hasn't AWS launched a PaaS? Lambda is so neutered that it doesn't really count.)