Google making AppEngine in the first place always felt weird to me. It was great for some web developers, but outside that use case, really not so much. But it came with a great collection of side technologies, which got unbundled (Datastore, etc) because there were folks (like me) who wanted to use the side tech but not AE itself (for many, many years you couldn't "import numpy" but people would still say "see? We have a cloud, it's called AppEngine").
Once enough things were unbundled from AE, and containers became popular, it wasn't really clear what AE provided that wasn't better solved by more standard tech.
Often times, Google leadership simply didn't understand what its own engineers and product managers knew. People told me for years "we can't do cloud because the profit margins are too small", and now look: Google is a perenially third-place in Cloud but has committed itself so much they can't even shut it down if they want to.
No, we all just migrated the decision of using GAE to using Cloud Functions / Run / Tasks, which is fine. Those are easier for Google to scale over time, than AppEngine.
The problem with AppEngine was that they had to heavily modify the runtimes for isolation... the JVM needed to be secured and that meant maintaining a separate fork, which also meant being perpetually always behind in versions. It also meant any upgrade had to go through a huge security evaluation.
So, moving to another process model, containers, worked much better.
My best friend Jeff started working on Objectify in 2009 after I convinced him to use GAE. I have built two businesses on it. One did $80m in revenue in the first year and I guarantee we couldn’t have done it without GAE.
Ugh, now you're making me explain myself due to your poor understanding of what I was saying and taking different comments in different threads out of context.
"We migrated"... meaning that over time, everyone is migrating from the concept of using GAE as a first choice, to using things like Run/Functions. Not that I actually physically took code for GAE and moved it to R/F. For example, my last project, I choose to use GCF, instead of GAE. The reason I went straight to GCF is because it is effectively what GAE has morphed into today. This isn't a slight on GAE at all. I've updated previous comment to hopefully clarify this for you.
Again, I have used GCP extensively since about 2009. By the way, much of what you use today was a result of things I did back when I co-founded the Jakarta Apache project, open sourced Tomcat from Sun, brought Lucene under the umbrella, blah blah blah... I've been around the internet since 1991.
Yea, they deprecated something. I even noted that the market is small for it in the thread. I built another solution in a short amount of time, and even gave it away because it really wasn't something people were using a lot of. It was a super niche product. That also wasn't even AppEngine, it was just a nice to have, for me, sub-service.
There was a point where people were upset about GCP and Google changed their whole deprecation policies to be more vocal and longer term about things.
I really don't understand your point. What's the big deal?
A better question is whether it’ll have improved or had price increases. GCP has had a bunch of increases lately, and you never know what will be next so you always have to guess at whether you’ll regret locking yourself more to a proprietary service.
AppEngine is going on, checks notes, 15 years now.