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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Cap is Only Part of the Story, we need PACELC

28 点作者 blopeur大约 3 年前

1 comment

remram大约 3 年前
This is framed as a new characterization of the properties of database servers, but isn&#x27;t just about whether the client waits for acknowledgment from the cluster?<p>It seems completely unrelated to the server&#x27;s consensus algorithm. Any client for any of those systems can proceed before the transaction is committed, it is faster but means that your transaction might disappear if the wrong node crashes.<p>How does the author end up with an empty column for &quot;PC&#x2F;EL&quot; in their table and not realize that &quot;choosing [low] latency&quot; (by not waiting for acknowledgment) is no longer guaranteed consistent?
评论 #31196167 未加载