So not all peer nodes are same. There are different types of peer nodes with different roles in the network: Endorser peer Anchor peer Orderer peer Endorser peer Peers can be marked as Endorser peer (Endorsing peer). Upon receiving the “transaction invocation request” from the Client application the Endorser peer Validates the transaction. Check certificate details and roles of the requester. Executes the Chaincode (Smart Contract) and simulates the outcome of the transaction. But it does not update the ledger. At the end of the above two tasks the Endorser may approve to disapprove the transaction. As only the Endorser node executes the Chaincode (Smart Contract) so there is no necessity to install Chaincode in each and every node of the network which increases the scalibility of the network. Anchor peer Anchor peer or cluster of Anchor peers is configured at the time of Channel configuration. Just to remind you, in Hyperledger Fabric you can configure secret channels among the peers and transactions among the peers of that channel are visible only to them. Anchor peer receives updates and broadcasts the updates to the other peers in the organization. Anchor peers are discoverable. So any peer marked as Anchor peer can be discovered by the Orderer peer or any other peer. Orderer peer Orderer peer is considered as the central communication channel for the Hyperledger Fabric network. Orderer peer/node is responsible for consistent Ledger state accross the network. Orderer peer creates the block and delivers that to all the peers. Orderer is built on top of a message oriented architecture. There are two options are currently available to implement Orderer peer: Solo: Suitable for development. Single point failure. Solo should not be used for the production ready network. Kafka: Production ready Hyperledger Fabric network uses Kafka as the Orderer implementation. Kafka is a messaging software that has high throughput fault tolerant feature.