The diagram below represents technology architecture viewpoint of hyperledger blockchain framework:
Hyperledger framework comprises of four key services/modules at a broader level. They are following:
- Membership services. Membership services comprise of components such as following:
- Registration: Registers/enrolls the new users
- Identity management: Manages identity of the users
- Audit management
- Blockchain services: Blockchain services comprise of following components used to manage consensus, storage and transactions:
- Consensus Manager: Used to implement consensus algorithm; Allows to plug-in extensible/customized consensus module. Consensus manager forms part of ordering service which validates the transaction using VSCC (validation system chaincode), create block of transaction and send them back to peer nodes.
- Distributed Ledger
- Ledger storage: Storage such as LevelDB or CouchDB can be used.
- P2P Protocol: Involves the peer nodes which act as endorsers and committers and how they interact with each other and ordering service (consenter). Endorsers endorses the proposal by executing chaincode using ESCC (endorser system chain code).
- Chaincode services: Chain code services comprise of containers and related services which are used to execute the chain code in a secured environment.
- Client SDKs/APIs: App uses client SDKs/APIs to connect to peer nodes.
Get further details from Hyperledger documentation.
Latest posts by Ajitesh Kumar (see all)
- Agentic Reasoning Design Patterns in AI: Examples - October 18, 2024
- LLMs for Adaptive Learning & Personalized Education - October 8, 2024
- Sparse Mixture of Experts (MoE) Models: Examples - October 6, 2024
I found it very helpful. However the differences are not too understandable for me