是“同时连接”在Firebase中的限制,因为它们出现? [英] Are "simultaneous connections" in Firebase as restrictive as they appear?

查看:76
本文介绍了是“同时连接”在Firebase中的限制,因为它们出现?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我很乐意使用Firebase作为我的HTML5移动应用程序的主要云存储服务,但是我很难弄清楚同时连接的限制是否会限制我将很多非实时用户限制为好了。

乍一看,看起来我只能拥有和我付费的连接一样多的用户。万人下载我的应用程序时会发生什么?如果我的应用不需要实时同步(轮询有时候完全正常),Firebase的架构是否仍然会限制并发用户的数量?我应该使用couchDB和VPS吗?

谢谢!

解决方案

<你需要少得多的预期用户总数。根据其定价常见问题,Firebase建议每约1440次访问一次。

(复制大部分来自评论,谢谢@Kato)

I would love to use Firebase as my primary cloud storage service for my HTML5 mobile apps, but I'm having trouble figuring out if the limit on simultaneous connections is going to restrict me from having a lot of non-realtime users as well.

At first glance, it looks like I can only have as many users as the connections I am paying for. What happens when 10,000 people download my app? If my app doesn't need real-time synchronization (polling is sometimes totally fine), is Firebase's architecture still going to limit the amount of concurrent users? Should I just go with couchDB and a VPS?

Thanks!

解决方案

You need many fewer concurrents than your total expected user count. Firebase recommends 1 concurrent for about every 1440 visits, per their pricing FAQ.

So, if you expect to have 10,000 visits, you'll likely see under 10 concurrents most of the time. This keeps you well below the 200 provided by the candle plan.

(Answer copied mostly from comments. Thanks @Kato)

这篇关于是“同时连接”在Firebase中的限制,因为它们出现?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆