Hyperledger Fabric 2.0.1 Documentationnodes to a distributed ordering service. Kafka (deprecated in v2.0) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache [https://kafka.apache.org/], the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site [https://kafka.apache.org/intro], but at a high level, Kafka uses the same conceptual “leader and follower”0 码力 | 760 页 | 10.21 MB | 1 年前3
Hyperledger Fabric 2.2.1 Documentationnodes to a distributed ordering service. Kafka (deprecated in v2.x) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache [https://kafka.apache.org/], the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site [https://kafka.apache.org/intro], but at a high level, Kafka uses the same conceptual “leader and follower”0 码力 | 848 页 | 11.56 MB | 1 年前3
Hyperledger Fabric 2.2.0 Documentationnodes to a distributed ordering service. Kafka (deprecated in v2.x) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache [https://kafka.apache.org/], the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site [https://kafka.apache.org/intro], but at a high level, Kafka uses the same conceptual “leader and follower”0 码力 | 820 页 | 10.90 MB | 1 年前3
Hyperledger Fabric 2.0 Documentationnodes to a distributed ordering service. Kafka (deprecated in v2.0) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache [https://kafka.apache.org/], the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site [https://kafka.apache.org/intro], but at a high level, Kafka uses the same conceptual “leader and follower”0 码力 | 821 页 | 10.22 MB | 1 年前3
Hyperledger Fabric 2.1.1 Documentationnodes to a distributed ordering service. Kafka (deprecated in v2.0) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache [https://kafka.apache.org/], the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site [https://kafka.apache.org/intro], but at a high level, Kafka uses the same conceptual “leader and follower”0 码力 | 816 页 | 10.25 MB | 1 年前3
Hyperledger Fabric 2.0.1 Documentationto a distributed ordering service. • Kafka (deprecated in v2.0) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes use Kafka and ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache, the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation, on the distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site, but at a high level, Kafka uses the same conceptual “leader and follower” configuration0 码力 | 533 页 | 8.37 MB | 1 年前3
Hyperledger Fabric 2.1 Documentationnodes to a distributed ordering service. Kafka (deprecated in v2.0) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache [https://kafka.apache.org/], the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site [https://kafka.apache.org/intro], but at a high level, Kafka uses the same conceptual “leader and follower”0 码力 | 904 页 | 10.95 MB | 1 年前3
Hyperledger Fabric 2.2.0 Documentationto a distributed ordering service. • Kafka (deprecated in v2.x) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes use Kafka and ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache, the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation, on the distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site, but at a high level, Kafka uses the same conceptual “leader and follower” configuration0 码力 | 577 页 | 9.03 MB | 1 年前3
Hyperledger Fabric 2.2.1 Documentationto a distributed ordering service. • Kafka (deprecated in v2.0) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes use Kafka and ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache, the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation, on the distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site, but at a high level, Kafka uses the same conceptual “leader and follower” configuration0 码力 | 575 页 | 8.55 MB | 1 年前3
Hyperledger Fabric 2.0 Documentationto a distributed ordering service. • Kafka (deprecated in v2.0) Similar to Raft-based ordering, Apache Kafka is a CFT implementation that uses a “leader and follower” node configuration. Kafka utilizes use Kafka and ZooKeeper on their own. Likewise, support for Kafka-related issues is handled through Apache, the open-source developer of Kafka, not Hyperledger Fabric. The Fabric Raft implementation, on the distributed streaming platform for use as a cluster of ordering nodes. You can read more about Kafka at the Apache Kafka Web site, but at a high level, Kafka uses the same conceptual “leader and follower” configuration0 码力 | 573 页 | 8.52 MB | 1 年前3
共 58 条
- 1
- 2
- 3
- 4
- 5
- 6













