Enterprise Blockchain and Hyperledger Fabric: Architecture, Peers, Orderers, Channels, Identity and the Transaction Flow

Blockchain Developer 60 min min read Updated: Nov 17, 2026 Intermediate
Enterprise Blockchain and Hyperledger Fabric: Architecture, Peers, Orderers, Channels, Identity and the Transaction Flow
Intermediate Topic 1 of 2

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 FabricEthereum (public)
AccessPermissionedPermissionless
IdentityCertificates, known membersPseudonymous addresses
Contracts calledChaincode (Go, Java, Node.js)Smart contracts (Solidity)
PrivacyChannels and private dataPublic by default
CurrencyNone requiredETH for gas
Transaction modelExecute, order, validateOrder, execute

Main Components

ComponentRole
OrganizationA 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
PeerHolds a copy of the ledger and runs chaincode. Endorsing peers simulate transactions
OrdererPuts transactions in order and creates blocks. Fabric offers Raft (crash fault tolerant) and, from v3, a BFT ordering option
ChannelA private sub-network with its own ledger and members
ChaincodeBusiness 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

  1. Client builds a transaction proposal and sends it to endorsing peers
  2. Peers execute (simulate) the chaincode and return signed results (endorsements)
  3. Client collects endorsements that satisfy the endorsement policy (for example 'Org1 AND Org2')
  4. Client sends the endorsed transaction to the ordering service
  5. Orderers sort transactions into blocks and deliver them to peers
  6. 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

  1. Why does Fabric not need a cryptocurrency?
  2. What is the difference between the blockchain and the world state?
  3. 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.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators