Open, Proven, Enterprise-grade DLT
One of the many compelling Fabric features is the enablement of a network of networks. Members of a network work together, but because businesses need some of their data to remain private, they often maintain separate relationships within their networks. For example, a purchaser may work with different sellers, selling the same product. The transactional relationship between the purchaser and each of the sellers should remain private and not visible across all sellers. This is made possible via the “channels” feature in Hyperledger Fabric if you need total transaction isolation, and the “private data” feature if you’d like to keep data private while sharing hashes as transaction evidence on the ledger (private data can be shared among “collection” members, or with a specific organization on a need-to-know basis. Rather than an open, permission-less system, Fabric offers a scalable and secure platform that sup-ports private transactions and confidential contracts. This architecture allows for solutions developed with Fabric to be adapted for any industry, thus ushering in a new era trust, transparency, and accountability for businesses.
Rather than an open, permission-less system, Fabric offers a scalable and secure platform that sup-ports private transactions and confidential contracts. This architecture allows for solutions developed with Fabric to be adapted for any industry, thus ushering in a new era trust, transparency, and accountability for businesses.
From the very beginning, Hyperledger Fabric was designed for enterprise use. It is intended as a foundation for developing applications or solutions with a modular architecture. Its modular and versatile design satisfies a broad range of industry use cases. It offers a unique approach to consensus that enables performance at scale while preserving privacy.
Unlike some other distributed ledger technologies that were originally designed for ad hoc, public use (where there is no privacy and no governance) which had to be significantly redesigned to add in support for permissions and privacy; Hyperledger Fabric was designed with these features as foundational. In this regard, Hyperledger Fabric has had a head start over many of the competing frame-works. For example, while there may be promise in some of the Ethereum 2.0 implementations, these are still mostly oriented to public network use, and in the Ethereum public network, the new architecture has still yet to be rolled out while Hyperledger Fabric has reached its version 2.0 milestone.
Below are some of the key features of Hyperledger Fabric and what differentiates it from other distributed ledger technologies.
- Permissioned architecture
- Highly modular
- Pluggable consensus
- Open smart contract model — flexibility to implement any desired solution model (account model, UTXO model, structured data, unstructured data, etc)
- Low latency of finality/confirmation
- Flexible approach to data privacy : data isolation using ‘channels’, or share private data on a needto-know basis using private data ‘collections’
- Support for EVM and Solidity
- Designed for continuous operations, including rolling upgrades and asymmetric version sup-port
- Governance and versioning of smart contracts
- Flexible endorsement model for achieving consensus across required organizations
- Queryable data (key-based queries and JSON queries)
Hyperledger Fabric Working
Traditional v/s Blockchain Business
Blockchain changes the way we do business
Advantages of Hyperledger Fabric
Model Approach of Fabric
Hyperledger modular umbrella approach
API in Hyperledger
API categeories in Hyperledger Fabric
Source : Internet and Hyperledger Fabric