[英]Google App Engine vs Firebase
I am trying to decide which option to go with. 我正在尝试决定使用哪个选项。 (or another if it is better) This is for a messaging type app where there will be high volume of notifications and database writes.
(或者如果更好的话,则为另一个)这适用于消息类型的应用程序,其中会有大量的通知和数据库写入。
Option 1 - Google App Engine using Cloud Endpoints and Cloud Datastore 选项1 - 使用Cloud Endpoints和Cloud Datastore的Google App Engine
Pros: 优点:
Cons: 缺点:
Option 2 - Firebase 选项2 - Firebase
Pros: 优点:
Cons: 缺点:
Option 3 - Would it be possible to combine Google Cloud Endpoints and Firebase? 选项3 - 是否可以组合Google Cloud Endpoints和Firebase?
First off take a look at the chart here from the Google docs for a great comparison and contrast of the different mobile app backend services they offer. 首先来看看图表这里从谷歌文档为一个伟大的比较和它们提供的不同的移动应用后端服务的对比。 Here is the chart:
这是图表:
My personal opinions are (Updated): 我的个人意见(更新):
Option 1 - Google App Engine using Cloud Endpoints and Cloud Datastore 选项1 - 使用Cloud Endpoints和Cloud Datastore的Google App Engine
Pros: 优点:
Cons: 缺点:
Option 2 - Firebase 选项2 - Firebase
Pros: 优点:
Cons: 缺点:
Read more in the link for possibly combining them. 阅读链接中的更多信息,以便将它们组合起来
I'm puzzled that many discussions of Firebase (including the question and answer above) fail to mention what, to me, is a very important difference: price. 我很困惑,很多关于Firebase的讨论(包括上面的问题和答案)都没有提到对我来说是一个非常重要的区别:价格。
Here is the Firebase price schedule. 这是Firebase的价格表。
Here are the Datastore and GAE pricing. 以下是数据存储和GAE定价。
It can be tricky to compare these, but my interpretation is that Firebase is very expensive. 比较这些可能很棘手,但我的解释是Firebase非常昂贵。
And this should come as no surprise. 这应该不足为奇。 GAE and datastore have to compete with similar services from Amazon, Microsoft etc., and the competition is fierce.
GAE和数据存储必须与来自亚马逊,微软等的类似服务竞争,竞争非常激烈。 Yes, these services are not as generic as infrastructure and SQL, of course, but they seem to be close enough that the prices remain competitive.
是的,这些服务当然不像基础设施和SQL那样通用,但它们似乎足够接近,价格仍然具有竞争力。
Firebase, on the other hand, is a premium service that competes with other backend services like Parse, and once you decide to use it I think it would be very difficult to switch. 另一方面,Firebase是一种优质服务,可与其他后端服务(如Parse)竞争,一旦您决定使用它,我认为切换非常困难。 It should come as no surprise that Google is pushing Firebase so hard - they are probably going to make a ton of money off of it since they can price it at such a premium.
谷歌如此努力地推动Firebase应该毫不奇怪 - 他们可能会从中赚取大量资金,因为他们可以以如此高的价格定价。
In my opinion, the upshot of this is that Firebase is a good choice for low volume and high-margin services, but if you plan to create a typical, consumer oriented, ad supported service that would depend on large volume to make money, then the cost of Firebase may kill your profit. 在我看来,这样做的结果是Firebase是低容量和高利润服务的不错选择,但是如果你计划创建一个典型的,面向消费者的,广告支持的服务,这将取决于大量赚钱,那么Firebase的成本可能会损害您的利润。
2017-10 Addition : 2017-10增加 :
I looked at Firebase again with the recent release of Firestore. 我最近发布的Firestore再次查看了Firebase。
I think it is important to be aware of another issue: using Firestore for an Android app means using the Firebase client library which is heavily dependent on Google Play Services, which means you can't deploy to non-Google devices including Amazon Fire tablets and (I believe) the entire Chinese market. 我认为重要的是要注意另一个问题:将Firestore用于Android应用程序意味着使用严重依赖于Google Play服务的Firebase客户端库,这意味着您无法部署到非Google设备,包括Amazon Fire平板电脑和(我相信)整个中国市场。
One thing that I have recently learned as I am struggling to find a solution for it is that firebase does not offer any work around device to device notification ; 我最近学到的一件事是,我正在努力寻找解决方案,因为firebase不提供任何有关设备到设备通知的工作; while it does offer server to device push notification and it's pretty easy to set up.
虽然它确实提供服务器到设备推送通知,但它很容易设置。 But the former lack of feature is very important and there's a conspiracy theory that it's because they are trying to push you to use other google products as well.
但前者缺乏功能是非常重要的,并且有一个阴谋论,因为他们试图推动你使用其他谷歌产品。
Or perhaps, since it wasn't developed at first they kept it the same. 或者,也许,因为它最初没有开发,所以它们保持不变。 I have figured that app engine is a way to connect the firebase and the devices for this purpose and so I would lean towards combining both firebase and other google products in this case app engine .
我认为app引擎是为此目的连接firebase和设备的一种方式,因此我倾向于将firebase和其他谷歌产品结合在这种情况下的app引擎中 。 If you plan to do more back end processing such as image processing, etc, then you are looking at app engine and compute engine for sure which could be integrated with Firebase resulting in a hypothetically powerful backend solution.
如果您计划进行更多后端处理(如图像处理等),那么您正在查看应用引擎和计算引擎,以确保哪些可以与Firebase集成,从而产生一个假设强大的后端解决方案。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.