分布式系统理论-技术博客集

分布式系统理论
编程技术 / houtizong 发布于 3年前 239

FLP

One famous theory in distributed computing, known as FLP after the authors Fischer, Lynch, and Patterson, proved that in a distributed system with asynchronous communication and process crashes, processes may not always agree on the one bit of configuration.

CAP

CAP, which stands for Consistency,Availability, and Partition-tolerance, says that when designing a distributed system we may want all three of those properties, but that no system can handle all three.

Paxos

Virtual Synchrony

Byzantine Faults/Failures - 拜占庭将军问题

Byzantine faults are faults that may cause a component to behave in some arbitrary (and often unanticipated) way. Such a faulty component might, for example, corrupt application state or even behave maliciously. Systems that are built under the assumption that these faults can occur require a higher degree of replication and the use of security primitives. Although we acknowledge that there have been significant advances in the development of techniques to tolerate Byzantine faults in the academic literature, we haven’t felt the need to adopt such techniques in ZooKeeper, and consequently we have avoided the additional complexity in the code base

上一篇：【Hadoop三】Centos7_x86_64部署Hadoop集群之编译Hadoop源代码

下一篇：分布式系统与框架

请勿发布不友善或者负能量的内容。与人为善，比聪明更重要！

<div  >  <h2>FLP</h2>  <p><span style="font-size: 16px;">One famous theory in distributed computing, known as FLP after the authors Fischer, Lynch, and Patterson, proved that in a distributed system with asynchronous communication and process crashes, processes may not always agree on the one bit of configuration</span>.</p>  <p>&nbsp;</p>  <h2>CAP</h2>  <p>&nbsp;</p>  <p><span style="font-size: 16px;">CAP, which stands for Consistency,Availability, and Partition-tolerance, says that when designing a distributed system we may want all three of those properties, but that no system can handle all three.</span></p>  <p>&nbsp;</p>  <h2>Paxos</h2>  <p>&nbsp;</p>  <h2>Virtual Synchrony<br /><br /> </h2>  <h2>Byzantine Faults/Failures&nbsp; - 拜占庭将军问题</h2>  <p><span style="font-size: 16px;">Byzantine faults are faults that may cause a component to behave in some arbitrary (and often unanticipated) way. Such a faulty component might, for example, corrupt application state or even behave maliciously. Systems that are built under the assumption that these faults can occur require a higher degree of replication and the use of security primitives. Although we acknowledge that there have been significant advances in the development of techniques to tolerate Byzantine faults in the academic literature, we haven’t felt the need to adopt such techniques in ZooKeeper, and consequently we have avoided the additional complexity in the code base</span></p>  <p>&nbsp;</p>  <p>&nbsp;</p>  <p>&nbsp;</p>  <p>&nbsp;</p> </div>

留言需要登陆哦

技术博客集 - 网站简介：
前后端技术：
后端基于Hyperf2.1框架开发,前端使用Bootstrap可视化布局系统生成
网站主要作用：
1.编程技术分享及讨论交流，内置聊天系统;
2.测试交流框架问题，比如：Hyperf、Laravel、TP、beego;
3.本站数据是基于大数据采集等爬虫技术为基础助力分享知识，如有侵权请发邮件到站长邮箱，站长会尽快处理;
4.站长邮箱：[email protected];

文章归档

文章标签

友情链接

首页
关于我们

Auther ·HouTiZong: 侯体宗的博客