Hey everyone, I thought this was such a great question I wrote an article
about it.
https://in.3wks.com.au/whats-not-to-love-about-google-app-engine-31de6454e746
I'd appreciate your thoughts and feedback.
Dave
On Sunday, November 5, 2017 at 3:20:34 PM UTC+11, timh wrote:
>
> I would agree
I would agree with Dave
Its is a very good platform. I have been using it since 2008.
I think to get the most out of it, you have to invest some effort
understanding how to use well.
The early adopters had to as there where really few scalable PAAS options
then.
Now there are a lot more
Hey Torsten, it's a great question. We're mystified too!
As others have said, initially it was an odd platform. Major web frameworks
(e.g. Django, Spring etc) didn't originally work out of the box for a
variety of reasons including the lack of a SQL database, file size limits,
slow startup
I really like it a lot. Especially for small teams, you don't have to
worry about dev-ops. Our company is running the SaaS service for 5+ years
with out dev-ops.
With all the improvement over the years, and the java8 available, it is
really a platform to go with.
I highly recommend. Just use
Hi, Torsten,
My 5 cents.
GAE allows measure "quality of code" in money. If the code is "bad", you
need a lot of GAE resources -> lot of money for serving your app.
This thing for some reason not liked by most developers.
:)
WBR, Vitaly.
--
You received this message because you are
Hi, Torsten,
Google App Engine was, I suspect, originally adopted by Python and Java
developers in the early days, it was seen as a very cheap alternative as a
Paas. Based around the no-sql datastore, it offered quite a few advantages
to say the heavy-ish load of say a straight Django based
This is a complicated question with many answers, most of which will be
based on opinions. :)
There are a number of companies that do build products on App Engine,
although not many of them make much noise about it. Snapchat and Kahn
Academy have historically written about their experiences. I
