Download Blockchain.CBDH.VCEplus.2019-06-07.126q.tqb

Simple key-value pairs - LevelDB is the default and is particularly appropriate when ledger states are simple key-value pairs. A LevelDB database is closely co-located with a network node - it is embedded within the same operating system process. CouchDB is a particularly appropriate choice when ledger states are structured as JSON documents because CouchDB supports the rich queries and update of richer data types often found in business transactions. Implementationwise, CouchDB runs in a separate operating system process, but there is still a 1:1 relation between a network node and a CouchDB instance. All of this is invisible to chaincode.Reference: https://hyperledger-fabric.readthedocs.io/en/release-1.3/ledger/ledger.html

To create a network according to an organization's structure, and to bootstrap a channel, we will need to generate the following artifacts: A genesis block, containing organization-specific certificates that serve to initialize the Fabric blockchain. Channel configuration information. Anchor peer configurations for each organization. An anchor peer serves as a fulcrum within an organization, for cross-organization ledger syncing using the Fabric gossip protocol.

Hyperledger explorer: Hyperledger explorer, which was originally contributed by IBM, Intel, and DTCC, can view, invoke, deploy or query blocks, transactions and associated data, network information (name, status, list of nodes), chain codes and transaction families, as well as other relevant information stored in the ledger.