When comparing Google App Engine vs Microsoft Azure Functions, 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 Microsoft Azure Functions is ranked 6th. 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 No server maintenance
Pro Deploy from Visual Studio
You can deploy apps directly from Visual Studio.
Pro Supports various languages
JavaScript, C#, F#, Python, PHP, Bash, Batch, and PowerShell
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.
Con Chains you to a vendor
When developing anything, it's best to be vendor independent. Tightly coupling your design to a vendor is just asking for trouble.
