Comparisons anchored on Hyperledger Fabric, the Apache-2.0 permissioned ledger platform from LF Decentralized Trust, against Hyperledger Besu.
Besu, an Ethereum client for public and private networks, against Fabric, a permissioned ledger with channels and chaincode: consensus options, smart contract languages, privacy models and the skills each needs.
How each keeps data private between participants now that Besu has removed Tessera private transactions: Fabric channels and private data collections against Besu permissioning, plugins and separate networks.
Two permissioned ledgers built for regulated business compared: Fabric's channels and chaincode against Corda's point-to-point flows, notaries and JVM CorDapps, plus licenses (both Apache-2.0) and the Corda 4 to Corda 5 split.
The enterprise blockchain shortlist compared: privacy model, consensus, smart contract languages, governance (LF Decentralized Trust versus R3) and the features Besu removed, such as Tessera privacy.
Which Fabric line to run or upgrade to: the maintained v2.5 and v3.1 lines, the Kafka orderer removed in 3.x, BFT ordering available only in 3.x, and how to plan the move for a production network.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.