Difference between revisions of "IT-SDK-Hyperledger-Fabric-Class"
Jump to navigation
Jump to search
Samerhijazi (talk | contribs) (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...") |
Samerhijazi (talk | contribs) |
||
| Line 3: | Line 3: | ||
*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 | ||
=Key Components= | =Key Components= | ||
| + | * Client Nodes | ||
| + | * Peer Nodes | ||
| + | ** AA | ||
| + | ** BB | ||
| + | * Orderer Nodes | ||
| + | * MSP (Membership Services Provider) | ||
| + | * Channels | ||
| + | * Chaincode | ||
| + | * Ledger | ||
==Peer Nodes== | ==Peer Nodes== | ||
* 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. | * 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. | ||
* 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. | * 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. | ||
* 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. | * 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. | ||
| + | =Basic workflow= | ||
| + | * The 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 to the peers. | ||
Revision as of 20:17, 16 February 2024
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 Components
- Client Nodes
- Peer Nodes
- AA
- BB
- Orderer Nodes
- MSP (Membership Services Provider)
- Channels
- Chaincode
- Ledger
Peer Nodes
- 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.
- 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.
- 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.
Basic workflow
- The 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 to the peers.
