协议更容易让人理解， 并且有很多成熟的工业算法实现，比如蚂蚁金服的 JRaft、Zookeeper 的 ZAB、Consul 的 Raft、 百度的 braft、Apache Ratis；因为 Nacos 是 Java 技术栈，因此只能在 JRaft、ZAB、Apache Ratis 中选择，但是 ZAB 因为和 Zookeeper 强绑定，再加上希望可以和 Raft 算法库的支持团队 随时沟通交流，因此选择了 列表变化的注册中心产品。 互联网软件行业普遍热捧开源产品，因为开源产品代码透明、可以参与共建、有社区进行交流和学 习，当然更重要的是它们是免费的。个人开发者或者中小型公司往往会将开源产品作为选型首选。 Zookeeper 是⼀款经典的服务注册中心产品（虽然它最初的定位并不在于此），在很长⼀段时间里， 它是国人在提起 RPC 服务注册中心时心里想到的唯⼀选择，这很大程度上与 Dubbo 在中国的普 及程度有关。Consul 服务的实例又会有划分为多个子集的需求，例如⼀个服务是多机房部署的，那么可能需要对每个机 房的实例做不同的配置，这样又需要在服务和实例之间再设定⼀个数据级别。 65 > Nacos 架构 Zookeeper 没有针对服务发现设计数据模型，它的数据是以⼀种更加抽象的树形 K-V 组织的，因 此理论上可以存储任何语义的数据。而 Eureka 或者 Consul 都是做到了实例级别的数据扩展，这

coordinator，纠结么 zookeeper etcd how to use etcd like zookeeper :) Distributed conponents 起因以及一些差异 not gonna cover every details zookeeper vs etcd 起因: reborndb是一个分布式redis集群框架 支持透明切换引擎 为了同时支持zookeeper和etcd zookeeper vs etcd zookeeper: session etcd: stateless zookeeper vs etcd 文件和目录的差异 zookeeper: 目录可以带value etcd: 目录就是纯粹的目录 zookeeper vs etcd 临时节点 zookeeper: 直接创建 etcd: 自己去更新ttl，用goroutine不断 去更新 如果watch了临时节点：这样又会不断 产生新的事件 zookeeper vs etcd zookeeper: getwatch etcd: watch after index ? how to choose index? what if index is far from current raft index? out of date zookeeper vs etcd RebornDB的getwatch实现

13 ���� ZooKeeper! Consul! etcd! AP����/� ����! ��! ���! ���! ���! CP����/� ����! ���! ��! ��! ��! �����! -! �����������! ���! ������! ��! ���! ���! ��������������� �����! ���! 31 Sentinel����� �������ZooKeeper�Nacos�Apollo�! ����! ����! ����! Sentinel��� ����! ����! ������! �����! ����! ����! �����

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 39.1. ZooKeeper cluster disaster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . capabilities on AMQP Mirror for Disaster Recovery • Journal Retention • Replication integrated with ZooKeeper • Connection Routers • Concurrency configuration for core bridges. • XPath filter expressions DistributedLockManager. Default is org.apache.activemq.artemis.lockmanager.zookeeper.CuratorDistributedLockManager which integrates with ZooKeeper. • properties - a list of property elements each with key and value

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 39.1. ZooKeeper cluster disaster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . capabilities on AMQP Mirror for Disaster Recovery • Journal Retention • Replication integrated with ZooKeeper • Connection Routers • Concurrency configuration for core bridges. • XPath filter expressions DistributedLockManager. Default is org.apache.activemq.artemis.lockmanager.zookeeper.CuratorDistributedLockManager which integrates with ZooKeeper. • properties - a list of property elements each with key and value

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 39.1. ZooKeeper cluster disaster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . capabilities on AMQP Mirror for Disaster Recovery • Journal Retention • Replication integrated with ZooKeeper • Connection Routers • Concurrency configuration for core bridges. • XPath filter expressions DistributedLockManager. Default is org.apache.activemq.artemis.lockmanager.zookeeper.CuratorDistributedLockManager which integrates with ZooKeeper. • properties - a list of property elements each with key and value

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 39.1. ZooKeeper cluster disaster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . capabilities on AMQP Mirror for Disaster Recovery • Journal Retention • Replication integrated with ZooKeeper • Connection Routers • Concurrency configuration for core bridges. • XPath filter expressions DistributedLockManager. Default is org.apache.activemq.artemis.lockmanager.zookeeper.CuratorDistributedLockManager which integrates with ZooKeeper. • properties - a list of property elements each with key and value

[https://raft.github.io/raft.pdf]. The other is Kafka [https://kafka.apache.org/] (which uses Zookeeper [https://zookeeper.apache.org/] internally). For information about currently available ordering services is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes a ZooKeeper ensemble for management purposes. The Kafka based ordering service has been available since Fabric scores of admirers, even those admirers will (usually) admit that deploying a Kafka cluster and its ZooKeeper ensemble can be tricky, requiring a high level of expertise in Kafka infrastructure and settings

[https://raft.github.io/raft.pdf]. The other is Kafka [https://kafka.apache.org/] (which uses Zookeeper [https://zookeeper.apache.org/] internally). For information about currently available ordering services is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes a ZooKeeper ensemble for management purposes. The Kafka based ordering service has been available since Fabric scores of admirers, even those admirers will (usually) admit that deploying a Kafka cluster and its ZooKeeper ensemble can be tricky, requiring a high level of expertise in Kafka infrastructure and settings

[https://raft.github.io/raft.pdf]. The other is Kafka [https://kafka.apache.org/] (which uses Zookeeper [https://zookeeper.apache.org/] internally). For information about currently available ordering services is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes a ZooKeeper ensemble for management purposes. The Kafka based ordering service has been available since Fabric scores of admirers, even those admirers will (usually) admit that deploying a Kafka cluster and its ZooKeeper ensemble can be tricky, requiring a high level of expertise in Kafka infrastructure and settings