Parse 的可扩展性如何? [英] How scalable is Parse?
问题描述
我一直在考虑将 Parse.com 的服务用于我的后端，但我对其可扩展性持怀疑态度.
I've been considering using Parse.com's service for my backend, but I'm skeptical about its scalability.
它真的能同时处理几千个用户吗?如果没有，他们有什么好的方法可以摆脱它吗?
Can it really handle several thousand simultaneous users? If not, is their any good way transitioning away from it?
推荐答案
我知道这个问题可能很老，但我想为其他可能正在考虑解析的人提供我的 2 美分......
I know the question may be old, but wanted to provide my 2 cents for others out there who may be considering parse....
在最简单的场景下，解析可能会很好地工作.一旦您需要扩展到更复杂的查询，我个人发现除了头疼之外别无他法.
Under the simplest of scenarios, parse may work well. As soon as you need to scale up to more complex queries, I have personally found nothing but headaches.
查询限制为 1000 条记录.最初，您可能认为这不是问题，直到您开始处理子查询，并意识到返回了奇怪的数据，因为子查询在没有警告或错误的情况下切断了记录.(仅供参考，除非您指定上限为 1000，否则默认为 100 条记录，因此如果您不注意，问题会更糟).
Queries are limited to 1000 records. Initially, you may think this is not an issue, until you start dealing with sub queries, and realize weird data is returned because the sub query cuts records off without warning or error. (FYI, the default is 100 records unless you specify a limit up to 1000, so the problem is even worse if you are not paying attention).
由于某种奇怪的原因，您在一分钟内可以发出计数查询的次数是有限制的.(而且这个限制似乎非常低).准备好尝试限制您的代码，以免达到此限制，否则会引发错误.
For some strange reason there is a limit to the number of times you can issue a count query in a min. (and this limit appears to be really low). Be prepared to try and throttle your code so you don't hit this limit, otherwise errors are thrown.
后台作业运行不可靠.我将后台作业设置为每 5 分钟运行一次，有时需要 20 多分钟才能开始作业.
Background Jobs do not run reliably. I have had a background job set to run every 5 min, and there are times it takes 20+ min before the job will kick in.
很多超时.这是最让我心痛的一个.A. 如果你有一个需要一段时间处理的云功能，你有大约 6 到 7 秒的时间来完成它，否则它会打断你.
B. 我感觉系统普遍不稳定.每隔一段时间，我就会遇到一些问题，这些问题似乎持续了大约一个小时左右，其中超时发生得更频繁(并且相对简单的函数应该立即返回).
Lots of Timeouts. This is the one that gives me the most heartburn.
A. If you have a cloud function that takes a while to process, you have about 6 or 7 seconds to get it done or it will cut you off.
B. I get the feeling that there is a general instability with the system. Periodically, I run into issues which seems to last for about an hour or so where timeouts happen more frequently (and with relatively simple functions that should return immediately).
我对使用 parse 的决定深感遗憾，我正在尽我所能让应用保持足够长的生命周期，以便我们获得资金，以便我们可以离开平台.如果有人有更好的解析替代方案，我会全力以赴.
I fully regret my decision to use parse, and I am doing all I can to keep the app alive long enough for us to get funding, so we can move off the platform. If anyone has any better alternatives to parse, I am all ears.
这篇关于Parse 的可扩展性如何?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
