Enterprise Blockchain and Hyperledger Fabric: Architecture, Peers, Orderers, Channels, Identity and the Transaction Flow
Why Enterprises Use Fabric
- Known participants: every member has a verified identity
- Privacy: only the right organizations see the data (channels, private data)
- No cryptocurrency needed to run the network
- Pluggable consensus and strong performance
- Open source under the Linux Foundation Decentralized Trust
Fabric Versus Ethereum
| Hyperledger Fabric | Ethereum (public) | |
|---|---|---|
| Access | Permissioned | Permissionless |
| Identity | Certificates, known members | Pseudonymous addresses |
| Contracts called | Chaincode (Go, Java, Node.js) | Smart contracts (Solidity) |
| Privacy | Channels and private data | Public by default |
| Currency | None required | ETH for gas |
| Transaction model | Execute, order, validate | Order, execute |
Main Components
| Component | Role |
|---|---|
| Organization | A company or member of the network |
| Membership Service Provider (MSP) | Defines who belongs to an organization using certificates |
| Certificate Authority (CA) | Issues identities to users and nodes |
| Peer | Holds a copy of the ledger and runs chaincode. Endorsing peers simulate transactions |
| Orderer | Puts transactions in order and creates blocks. Fabric offers Raft (crash fault tolerant) and, from v3, a BFT ordering option |
| Channel | A private sub-network with its own ledger and members |
| Chaincode | Business logic that reads and writes the ledger |
The Ledger
- Blockchain: the immutable history of transactions
- World state: the current value of each key, kept in a database such as LevelDB or CouchDB for fast queries
Execute-Order-Validate Flow
- Client builds a transaction proposal and sends it to endorsing peers
- Peers execute (simulate) the chaincode and return signed results (endorsements)
- Client collects endorsements that satisfy the endorsement policy (for example 'Org1 AND Org2')
- Client sends the endorsed transaction to the ordering service
- Orderers sort transactions into blocks and deliver them to peers
- Peers validate each transaction (policy satisfied, no conflicting version) and commit to the ledger and world state
Why this order? Executing before ordering lets different organizations check results first, and it improves scalability because only endorsers run the code.
Version Note
Hyperledger Fabric 3.x added a BFT ordering service and continues to evolve. The 2.5 line was maintained as a long-term-support release for production users. Check the Fabric documentation for the release that suits your project.
Practice
- Why does Fabric not need a cryptocurrency?
- What is the difference between the blockchain and the world state?
- Describe the six steps of a Fabric transaction
Conclusion
Fabric is a permissioned enterprise blockchain with known identities, channels for privacy and an execute-order-validate flow that uses endorsement policies.
Quick Summary: why; vs Ethereum; components; ledger; flow; versions.

