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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Application-Level Consensus [pdf]

53 点作者 hugothefrog大约 8 年前

4 条评论

ergl大约 8 年前
Jane Street uses the same approach to build their exchange [0]. Like the doc says, it can be great to replay some sequence of messages in dev to reproduce issues, and to give fault-tolerance to the system.<p>One downside is that, if all your nodes are using the same application code, simply replaying the log might not help as all nodes might hit exactly the same bug with the same sequence of transitions.<p>[0] There&#x27;s an overwiev of their infrastructure here <a href="https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=b1e4t2k2KJY" rel="nofollow">https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=b1e4t2k2KJY</a>
评论 #14028713 未加载
gawi大约 8 年前
This is very interesting. I have no doubts that not having to deal with fault tolerance at the application level compensates for the efforts to put in place this architecture. And yes, in my opinion, &quot;application-level consensus&quot; is the perfect term to designate this architecture.
评论 #14023086 未加载
silviatorres大约 8 年前
Hi there!! looks like there was some minimal mistakes on the text and the document was updated: <a href="http:&#x2F;&#x2F;weareadaptive.com&#x2F;wp-content&#x2F;uploads&#x2F;2017&#x2F;04&#x2F;Application-Level-Consensus.pdf" rel="nofollow">http:&#x2F;&#x2F;weareadaptive.com&#x2F;wp-content&#x2F;uploads&#x2F;2017&#x2F;04&#x2F;Applicat...</a>
eternalban大约 8 年前
Try &#x27;Edge-Coherence&#x27;.