问题描述
我可以看到订购者有3种类型.当我部署结构网络时，最多使用2种类型.
I can see there are 3 types of orderer. When I deploy a fabric-network up to 2 types are used.
https://hub.docker.com/r/hyperledger/fabric-订购者/ https://hub.docker.com/r/hyperledger/fabric-kafka/
https://hub.docker.com/r/hyperledger/fabric-ca-orderer/
订单文档描述了用法
https://github.com/hyperledger/fabric/blob /master/orderer/README.md
但是我不希望在网络中看到Fabric-Orderer和Fabric-kafka容器.
but I do not expect to see fabric-orderer and fabric-kafka containers in a fabric network.
我在这里误会什么?
推荐答案
Hyperledger Fabric的体系结构允许多种类型的订购服务.该体系结构的核心是一个通用的原子广播接口.
The architecture for Hyperledger Fabric allows for multiple types of ordering services. At the heart of the architecture is a common atomic broadcast interface.
订购者接口是在订购者可执行文件中实现的，该可执行文件打包为结构订购者Docker映像.
The orderer interfaces are implemented in the orderer executable which is packaged as the fabric-orderer Docker image.
订购者有两种配置模式:
There are two configuration modes for the orderer:
1)独奏-这是一个独立的单流程订购程序，主要用于开发和测试期间(尽管没有什么可以阻止某人将其用于生产中-它只是不能容错的)
1) Solo - this is a standalone, single process orderer primarily for use during development and test (although nothing would stop someone from using it for production - it would just not be fault tolerant)
2)Kafka-这利用Kafka作为共识"机制来使多个订购者进程崩溃并容错并订购事务.在这种情况下，多个订购者进程与Kafka集群通信，以确保每个订购者进程接收事务并以相同顺序生成块.订购程序进程(或Fabric-Orderer容器)与Kafka集群通信(可以使用fabric-kafka和fabric-zookeeper Docker映像运行).
2) Kafka - this leverages Kafka as the "consensus" mechanism to make multiple orderer processes crash fault tolerant and order transactions. In this case, multiple orderer processes communicate with a Kafka cluster which ensures that each orderer process receives transactions and generates blocks in the same order. The orderer process (or fabric-orderer containers) communicate with a Kafka cluster (which can be run using the fabric-kafka and fabric-zookeeper Docker images).
这篇关于同一网络中的fabric-kafka和fabric-order容器的用例是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！