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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Ask HN: What's the difference between CRDT vs. Eventual Consistency?

3 点作者 KiranRao0将近 4 年前
Hi HN, I&#x27;ve seen several articles about CRDTs [1] lately and I don&#x27;t fully understand how they&#x27;re different from the concept of eventual consistency [2] in distributed computing.<p>[1]: https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Conflict-free_replicated_data_type<p>[2]: https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Eventual_consistency

1 comment

jka将近 4 年前
Yep, they&#x27;re closely related. Here&#x27;s my attempt to distinguish the ideas, let me know whether this makes sense:<p>Eventual Consistency is a property that can be used to describe a datastore or an individual datastructure.<p>So we could say that, for example, &quot;Cassandra is an eventually-consistent database&quot;, or that &quot;the Elasticsearch cluster is eventually-consistent&quot;.<p>One of the core features of CRDTs is that they are, by design, always eventually consistent.<p>That&#x27;s useful since it allows CRDTs to be used in environments where peers may temporarily go offline, and would like to catch up with other peer changes (and share their own) - eventually - when they are back online.
评论 #28028473 未加载