implementations. The first is based on the etcd library [https://coreos.com/etcd/] of the Raft protocol [https://raft.github.io/raft.pdf]. The other is Kafka [https://kafka.apache.org/] (which uses Zookeeper [https://zookeeper patch release. Raft ordering service Introduced in v1.4.1, Raft [https://raft.github.io/raft.pdf] is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol in etcd [https://coreos.com/etcd/]. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers. Raft ordering services should be

implementations. The first is based on the etcd library [https://coreos.com/etcd/] of the Raft protocol [https://raft.github.io/raft.pdf]. The other is Kafka [https://kafka.apache.org/] (which uses Zookeeper [https://zookeeper patch release. Raft ordering service Introduced in v1.4.1, Raft [https://raft.github.io/raft.pdf] is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol in etcd [https://coreos.com/etcd/]. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers. Raft ordering services should be

implementations. The first is based on the etcd library [https://coreos.com/etcd/] of the Raft protocol [https://raft.github.io/raft.pdf]. The other is Kafka [https://kafka.apache.org/] (which uses Zookeeper [https://zookeeper patch release. Raft ordering service Introduced in v1.4.1, Raft [https://raft.github.io/raft.pdf] is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol in etcd [https://coreos.com/etcd/]. Raft follows a “leader and follower” model, where a leader node is elected (per channel) and its decisions are replicated to the followers. Raft ordering services should be

currently offers two CFT ordering service implementations. The first is based on the etcd library of the Raft protocol. The other is Kafka (which uses Zookeeper internally). For information about currently available the patch release. 2.2 Raft ordering service Introduced in v1.4.1, Raft is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol in etcd. Raft follows a “leader and model, where a leader node is elected (per channel) and its decisions are replicated to the followers. Raft ordering services should be easier to set up and manage than Kafka-based ordering services, and their

currently offers two CFT ordering service implementations. The first is based on the etcd library of the Raft protocol. The other is Kafka (which uses Zookeeper internally). For information about currently available the patch release. 2.2 Raft ordering service Introduced in v1.4.1, Raft is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol in etcd. Raft follows a “leader and model, where a leader node is elected (per channel) and its decisions are replicated to the followers. Raft ordering services should be easier to set up and manage than Kafka-based ordering services, and their

currently offers two CFT ordering service implementations. The first is based on the etcd library of the Raft protocol. The other is Kafka (which uses Zookeeper internally). For information about currently available the patch release. 2.2 Raft ordering service Introduced in v1.4.1, Raft is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol in etcd. Raft follows a “leader and model, where a leader node is elected (per channel) and its decisions are replicated to the followers. Raft ordering services should be easier to set up and manage than Kafka-based ordering services, and their

service implementation based on the etcd library [https://coreos.com/etcd/] of the Raft protocol [https://raft.github.io/raft.pdf]. For information about currently available ordering services, check out our currently available implementations of the ordering service, with a particular focus on the recommended Raft ordering service implementation. What is ordering? Many distributed blockchains, such as Ethereum an ordering node. Raft (recommended) New as of v1.4.1, Raft is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol [https://raft.github.io/raft.pdf] in etcd [https://coreos

● 分层 ● Make it right and make it fast. ● 测试很重要 ● 简单易用 ● 和社区结合 架构 TiKV TiKV TiKV TiKV Raft Raft Raft TiDB TiDB TiDB ... ... ... ... ... Placement Driver (PD) Control flow: Balance / Failover Physically, data is stored in RocksDB ● We build a Raft layer on top of RocksDB ○ What is Raft? ● Written in Rust! TiKV API (gRPC) Transaction MVCC Raft (gRPC) RocksDB Raw KV API (https://github.com/pingc Region 4:[p-t] Raft group Storage stack 2/2 ● Data is organized by Regions ● Region: a set of continuous key-value pairs RPC (gRPC) Transaction MVCC Raft RocksDB ··· Raft ● 复制/分裂/负载均衡 Region

service implementation based on the etcd library [https://coreos.com/etcd/] of the Raft protocol [https://raft.github.io/raft.pdf]. For information about currently available ordering services, check out our currently available implementations of the ordering service, with a particular focus on the recommended Raft ordering service implementation. What is ordering? Many distributed blockchains, such as Ethereum an ordering node. Raft (recommended) New as of v1.4.1, Raft is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol [https://raft.github.io/raft.pdf] in etcd [https://coreos

service implementation based on the etcd library [https://coreos.com/etcd/] of the Raft protocol [https://raft.github.io/raft.pdf]. For information about currently available ordering services, check out our currently available implementations of the ordering service, with a particular focus on the recommended Raft ordering service implementation. What is ordering? Many distributed blockchains, such as Ethereum an ordering node. Raft (recommended) New as of v1.4.1, Raft is a crash fault tolerant (CFT) ordering service based on an implementation of Raft protocol [https://raft.github.io/raft.pdf] in etcd [https://coreos