# Hyperledger Fabric Workflow ### Feature * a protocol for B2B and B2C transactions * a permissioned ledger, peers have different roles * peers maintain their one ledger per channel that they are subscribed to * less computations compared to permissionless * industry-focused use cases * identity and auditability * private transactions and confidential contracts ![](https://i.imgur.com/JXEtrWB.png =500x) ### Architecture ![](https://i.imgur.com/nttCMaV.png =500x) ### Workflow * **Client**: any specific application/portal serving specific organization/business activities * **Endorser peer**: * input: "transaction invocation request the Client * validates the transaction * executes the Chaincode and simulates the outcome of the transaction * output: approve or disapprove the transaction * **Anchor peer**: receives updates and broadcasts them to the other peers in the same Organization * **Orderer peer**: responsible for consistent Ledger state across the network * creates the block and delivers it to all the peers in different Organizations ![](https://i.imgur.com/EbrQLAb.png =500x) ### Application Model ![](https://i.imgur.com/Yp8hy4g.png =200x) ### Reference * [Hyperledger Whitepaper](https://blockchainlab.com/pdf/Hyperledger%20Whitepaper.pdf) * [Medium, Prachi Gopalani](https://medium.com/geekculture/how-hyperledger-fabric-blockchain-works-explained-9a93d52d044c) * [Medium, Muntasir Mamun](https://medium.com/coinmonks/how-does-hyperledger-fabric-works-cdb68e6066f5)