Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Google App Engine vs Kuzzle, the Slant community recommends Kuzzle for most people. In the question“What are the best Backend as a Service providers for webapps?” Kuzzle is ranked 2nd while Google App Engine is ranked 6th. The most important reason people chose Kuzzle is:
Supports REST, WebSockets and MQ protocols.
Question 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 Multiprotocol
Supports REST, WebSockets and MQ protocols.
Pro Realtime through filters
You do not connect to classic rooms but to search filters and can be warned of changes on permanent storage or volatile one.
Pro Open Source
Kuzzle is open source and it's released under the Apache 2 License.
Pro Javascript SDK
A fully documented javascript SDK exists.
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 May have issues since it's stil la relatively young project
Kuzzle is (as of February 2nd, 2015) in alpha version and approaching beta.
