In Fabric development, testing chaincode is a bit of a headache. First, in a real deployment, storage and queries in chaincode depend on the state database on the peer, so you cannot test it directly on your local machine. Second, chaincode runs inside a container, which makes it hard to get at the logs printed by your code.
My earlier posts on deploying Fabric all assumed a single machine. In a real production environment, nodes are usually spread across several physical machines depending on the use case, and the main challenge is how nodes on different hosts communicate over the network.
Adding a new organization to a Fabric network while it is running is quite involved, and there is very little material on it online. Most of what exists is based on simple examples like first-network, and adds the organization by starting a cli container. There is almost nothing aimed at real applications. This post shows how to add an organization dynamically by calling the SDK from an application.
The initial number of peers in a Fabric network is fixed when the network is created, but in real application scenarios you may need to add peers to an organization dynamically. Using balance-transfer v1.0 as an example (2 orgs, 4 peers), this post shows how to add a third peer to org1.
The organization (Org) and channel names are two fairly important configuration parameters of a Fabric network. Both are already set in the samples Fabric provides: the organizations are usually named "Org1" and "Org2", and the channel "mychannel". In real application development, however, you usually need custom organization and channel names. Here I use balance-transfer, the sample closest to a real application, to show how to set custom organization and channel names.
This post introduces Fabric's application development model and the Node SDK, and runs a simple Fabric application sample.
This post runs the Building Your First Network sample from fabric-samples. The network has 4 peers split across 2 organizations, plus a single orderer. A cli container is also needed to interact with the network nodes.
Hyperledger Fabric 1.0 is built on PKI (Public Key Infrastructure) and introduces the MSP (Membership Service Provider) module, which generates digital certificates to identify members and manage their identities.
Fabric CA is the certificate authority for Hyperledger Fabric. It provides the following functions: registering and enrolling users, and issuing and managing digital certificates.
This post covers how to install and deploy a Fabric environment on Ubuntu and CentOS, and how to run an example that starts a Fabric network on a single machine.
