This question/concern keeps popping up every few months for years now. Being a very early GAE user, I have my opinions and history based analysis that I have posted before. Recent signals, having attended Next as well, make me more optimistic than usual.
Today I want to add a new perspective: The question really is how much risk do you want to take? Recently the US stock market listed Snap. When you get listed in the US you are required to provide the investors an S-1 that contains all the risks of investing in this offering. Open the Snap S-1 here <https://www.sec.gov/Archives/edgar/data/1564408/000119312517029199/d270216ds1.htm> and search for Google and read these paragraphs. Bottom line, Snap says "we are alive as long as Google Cloud is alive". Then look at this Quora thread: https://www.quora.com/How-does-Snapchat-use-Google-App-Engine Bottom line between those two, for now Snap, a US public company, is alive as long as GAE Standard is alive. So, I conclude that Google will be committed to GAE Std. for a while. These are the kind of signals to look for; "formal statements" are good for few days, and we have seen many of those over the years, but can come and go as fast as an e-mail can be written. Does anybody else know of other such "too big to fail" successes built on GAE Std? The more of those the more confident I would be... Another signal of course is where Google puts its investment dollars. In the early 2010s timeframe Google puts all its (few at the time) eggs in GAE. The marketplace did not reward this approach so Google increased its Cloud investment and shifted all of it to build a better AWS because this is what the volume enterprise and startup market seemed to want. However GAE survived and remains a competitive advantage and differentiator for GCP, so I hope Google delivers and puts back more investment to GAE now. PK www.gae123.com PS If the two GAEs merge downstream I am fine as long as I do not have to revisit (ie modify/test etc) code in production that has been working for years. The more of that I would have to do the more negative I would become of such a development. On Friday, March 31, 2017 at 5:39:29 AM UTC-7, Tim Consolazio wrote: > > I've been noticing some things: > > - App Engine support shunted over to Stack Overflow (so...a non-Google > community resource). > - Mail API pretty much deprecated (no more quota expansions, 100 email > limit). > - Deprecation of Channel API (sure we have Firebase, but still...what's > the commitment to that?) > - No Java 8 (and 7 was a long time in coming). > - Gradual deprecation of local SDK in favor of remote/virtual dev (which > to me is unacceptable, I depend on that local SDK). > > I frequently recommend App Engine (and I've built quite a few apps on it). > I've been a rogue evangelist of the platform for years (since it was > released in fact), and have been contracted by Google three times to build > applications using it. So I'm not a hater in any way. > > But I can't look at these events (particularly the Stack Overflow thing) > and ignore the impression that App Engine is beginning to feel more like a > side project rather than a commercial offering with full resource > commitment by the vendor. > > Curious about a formal statement of commitment here, and a complete > roadmap of what we can reasonably expect over say, the next two years. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/49fdae08-8fcf-4f38-a9fc-d013b8fcd439%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
