TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Real-Time Databases Explained: Why Meteor, Rethink, Parse and Firebase Don't Scale

20 点作者 DivineTraube超过 7 年前

2 条评论

btown超过 7 年前
Written format: <a href="https:&#x2F;&#x2F;medium.baqend.com&#x2F;real-time-databases-explained-why-meteor-rethinkdb-parse-and-firebase-dont-scale-822ff87d2f87" rel="nofollow">https:&#x2F;&#x2F;medium.baqend.com&#x2F;real-time-databases-explained-why-...</a><p>And the paper for their more scalable alternative: <a href="https:&#x2F;&#x2F;www.cl.cam.ac.uk&#x2F;~mks40&#x2F;pubs&#x2F;vldb_2017.pdf" rel="nofollow">https:&#x2F;&#x2F;www.cl.cam.ac.uk&#x2F;~mks40&#x2F;pubs&#x2F;vldb_2017.pdf</a><p>The devil will absolutely be in the details, but the speaker&#x2F;author identifies a real pain point that bolting on a replication-log tailing system to provide realtime capabilities results in numerous write bottlenecks unless the system is architected from scratch to avoid them.
code-is-code超过 7 年前
Meteor has the op-log-driver which calculates query-result for changes instead of running the wohle query again. Same comes with rxdb where it&#x27;s called query-change-detection.
评论 #15481084 未加载