System Architecture

The above diagram depicts the overall architecture for the scenario mentioned above. Each Organization will have their own peer node there will be an orderer(O) node connected to the same channel as peer nodes to insert the transactions into the ledger. The organizations have their own user certificates generated by the fabric-ca binaries which are used to sign the transactions done by the web applications of the respective organizations.

Peer nodes have user roles to restrict the access of chaincode functionality based on the hierarchy. So a Manager role will have access to all the functions whereas an employee will have restricted view access.

The Data starts flowing from the producer/supplier and additional details regarding the product will get appended and stored at each stage of the transactions.

The current scope of the project is limited to two organizations one being the supplier and the other being the seller. The network is used to record the transactions between two organizations in their own ledger.

Architecture flow

1. The blockchain operator creates a Docker Kubernetes Service.

2. Users create a Hyperledger Fabric network on a Docker Kubernetes Service, and the operator installs and instantiates the smart contract on the network.

3. The Node.js application server uses the Fabric SDK to interact with the deployed network on the local or cloud platform where Hyperledger is.

4. The React UI uses the Node.js application API to interact and submit transactions to the network.

5. The user interacts with the supply chain application web interface to update and query the blockchain ledger and state.