When comparing Google App Engine vs Cloud Run, the Slant community recommends Google App Engine for most people. In the question“What are the best serverless frameworks?” Google App Engine is ranked 2nd while Cloud Run is ranked 11th. The most important reason people chose Google App Engine is:
Google App Engine integrates with Google's CDN out of the box and it distributes your application's assets through that, increasing loading speed considerably.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Increases application speed considerably
Google App Engine integrates with Google's CDN out of the box and it distributes your application's assets through that, increasing loading speed considerably.
Pro Easy to use
Google App Engine is very easy to use. All you need to do is install the SDK (which in itself is easy as well, and the documentation is very heplful) and run the command needed depending on the type of project to deploy it.
For example, to deploy a golang application, you run golang deploy
inside the project folder and it will be automatically deployed.
Pro Flexible
The system supports arbitrary code and dependencies, since it is based in containers rather than a particular programming language. This makes it far more flexible than most of the other options which require a specific language.
Pro Portable
The code doesn't need to make any Google-specific assumptions and can be easily deployed in other kinds of environments and frameworks.
Pro Secure
Cloud Run includes Identity & Access Management (IAM) integration, so that it is possible to limit access to specific microservices rather than granting wide access.
Pro Cost effective
Google's pricing for Cloud Run involves only charging when the service is in use, with the ability for the service to scale-down-to-zero, making it economical to use Cloud Run with microservices and websites that receive relatively low or spiky traffic.
Cons
Con Not a core Google product faces uncertin future
Google is notorious with flipping on technology directions, this product is clearly not the focus of Google.
Con Expenses are very hard to control
The monitoring for expenses is limited at best.
Con Problematic support even in the paid grade
Con No SQL database available
Google App Engine uses Google's NoSQL cloud database. There's no option to use a SQL database with your application.