A consensus service is responsible for providing the interface to the consensus mechanism. This serves as a module that is pluggable and receives the transaction from other Hyperledger entities and executes them under criteria according to the type of mechanism chosen.
Consensus in Hyperledger V1 is implemented as a peer called orderer, which is responsible for ordering the transactions in sequence into a block. Orderer does not hold smart contracts or ledgers. Consensus is pluggable and currently, there are two types of ordering services available in Hyperledger Fabric:
- SOLO: This is a basic ordering service intended to be used for development and testing purposes.
- Kafka: This is an implementation of Apache Kafka, which ...
