Snapchat was (is?) built on AppEngine and they signed a 5 year 3 billion dollar contract with GCP. I wouldn't be surprised if AppEngine is hanging by a thread outside of a few large users as GCP devs have on multiple occasions signaled new projects with the intention of replacing AppEngine (I forget which ones, feel free to verify that anecdote yourself).
AppEngine is just one product in Google Cloud, and the first they released in 2008. Of course there will be new versions and eventually new products that are recommended like VMs, GKE, Cloud Functions, Cloud Run, and more.
It's still supported and has plenty of usage so I don't see it as "hanging by a thread" unless you have more data than things that people said but apparently you forgot?
So what? I can give you a point-by-point rebuttal of everything on that page.
> The standalone legacy SDK and appcfg tooling
Just use the newer `gcloud` command-line tool.
> Go 1.9 (GA) and Node.js 8 (GA)
Upgrade your language man. This is PaaS. You're expected to keep your app up to date.
> Admin API v1beta4/v1beta5
These are beta versions of the API. Why don't use migrate to the GA versions?
Etc, etc. In fact the large number of deprecations on that page only shows how rapidly new features and runtimes and frameworks are being developed to replace old ones.
While AWS has deprecated runtimes, if you have an old running version of Node for instance on lambda, it will run forever. It will force you to upgrade to a newer version the next time you update the lambda.
As far as I know, AWS has never discontinued a service or turned off an API. They may deprecate a feature or make it unavailable for new accounts or regions.
Heck AWS still supports running an EC2 instance outside of a VPC if your account is old enough,SimpleDB , and using S3 as a BitTorrent seed for old regions.
