What are the pitfalls of Google App Engine?

A

alex_dm2014-08-14 10:37:06

Google Cloud Platform

alex_dm, 2014-08-14 10:37:06

Hello.
We are starting a fairly large project (API, partner site, client site, developer site with SDK documentation). Since human resources are now limited, and the load is supposed to be not small, we decided to use Google App Engine as a platform so as not to waste time and energy on server support.
The backend will be in PHP, Laravel was chosen as the framework (including because it runs relatively painlessly in Google clouds).
What are the problems / pitfalls in using this zoo?

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

V

Vyacheslav Plisko, 2014-08-14
@alex_dm

Why do you need this turd that for years could not introduce php support when there is a wonderful https://forge.laravel.com/

B

bogolt, 2014-08-14
@bogolt

>Starting a pretty big project
>decided to use Google App Engine as a platform
When Google decides to close their next "unused service to make something even cooler" you will have a lot of fun.
IMHO, in matters of key areas of their programs, one cannot be so dependent on anyone else.
ps. Google isn't the only platform that gives you the ability to develop apps, but I wouldn't jump on any of them without good reason.

M

m0nym, 2018-05-18
@m0nym

The main pitfall is a terribly strong binding to the unique Google AppEngine APIs.
The second pitfall, it would seem obvious, but not everyone sees through - the software needs to be developed not as they are used to for a regular server, but with the expectation of "12 factors".
Third, a consequence of the misunderstood second - stupid software will eat a lot of dough. You should always think before you force the program to do an unnecessary action.