Difference between revisions of "IT-SDK-Hyperledger-Fabric-Class"

From wiki.samerhijazi.net
Jump to navigation Jump to search
(Created page with "=Ref.= *https://medium.com/xord/hyperledger-fabric-architecture-a-deep-dive-cea478f39765 *https://www.spydra.app/blog/architecture-of-hyperledger-fabric-an-in-depth-guide =Key...")
 
(→‎Ref.)
 
(5 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
*https://medium.com/xord/hyperledger-fabric-architecture-a-deep-dive-cea478f39765
 
*https://medium.com/xord/hyperledger-fabric-architecture-a-deep-dive-cea478f39765
 
*https://www.spydra.app/blog/architecture-of-hyperledger-fabric-an-in-depth-guide
 
*https://www.spydra.app/blog/architecture-of-hyperledger-fabric-an-in-depth-guide
 +
*https://developer.ibm.com/articles/blockchain-basics-hyperledger-fabric/
 +
*https://hyperledger-fabric.readthedocs.io/en/release-1.4/arch-deep-dive.html
 +
 
=Key Components=
 
=Key Components=
−
==Peer Nodes==
+
* Client Nodes (Submitting Client)
−
* Endorsing Peers: These peer nodes receive transaction proposals from clients, execute the chaincode, and return the results along with an endorsement signature. Endorsing peers don't update the ledger but are critical for achieving transaction endorsement.
+
* Peer Nodes (Endorsing Peers) or (Committing Peers)
−
* Committing Peers: After receiving the endorsed transaction, committing peers validate the endorsements and ensure the correctness of the endorsements before committing the transaction to the ledger.
+
* Orderer Nodes (Ordering Service)
−
* Anchor Peers: These are specific peers in each organization that maintain communication with peers in other organizations. They are used to facilitate cross-organization communication.
+
* MSP (Membership Services Provider)
 +
* Channels
 +
* Chaincode
 +
* Ledger
 +
=Basic workflow=
 +
* The submitting client creates a transaction and sends it to endorsing peers of its choice.
 +
* The endorsing peer simulates a transaction and produces an endorsement signature.
 +
* The submitting client collects an endorsement for a transaction and broadcasts it through ordering service.
 +
* The ordering service delivers a transactions (blocks) to the committing peers.
 +
* The committing peers appended transaction to the Ledger.

Latest revision as of 18:32, 30 October 2024

Ref.

Key Components

  • Client Nodes (Submitting Client)
  • Peer Nodes (Endorsing Peers) or (Committing Peers)
  • Orderer Nodes (Ordering Service)
  • MSP (Membership Services Provider)
  • Channels
  • Chaincode
  • Ledger

Basic workflow

  • The submitting client creates a transaction and sends it to endorsing peers of its choice.
  • The endorsing peer simulates a transaction and produces an endorsement signature.
  • The submitting client collects an endorsement for a transaction and broadcasts it through ordering service.
  • The ordering service delivers a transactions (blocks) to the committing peers.
  • The committing peers appended transaction to the Ledger.
Retrieved from "http://wiki.samerhijazi.net/index.php?title=IT-SDK-Hyperledger-Fabric-Class&oldid=3086"