Table 2-28 Component breakdown of the peer’s containers Container Description Peer This container holds the smart contracts that are installed and instantiated on it.  Also, this containers holds the ledger for all the channels that the peer is joined  to. CouchDB This container is the world state database for each channel that the peer is joined  to. The world state contains the current value for all the assets recorded on the  blockchain ledger. An analogy would be a potato that is an asset in the  blockchain network. Imagine that the potato is passed around 100 times. The  world state database would contain the information of who has the potato on the  100th transfer. It is the most up-to-date information in regard to a specific asset.  By default, the world state database is CouchDB. Smart Contract This container is actually a docker-in-docker (dind) container. The smart  contracts are stored here, when there is an installation and instantiation of a  smart contract.  Log Collector This container is responsible for the log messages that are coming from the  smart contract container (dind). gRPC This container contains the processes that allow the console (user interface) to  communicate with this node (peer). It connects the IBM Cloud Private Instance  to the IBM Blockchain for Multicloud instance.  2.4.6 Resource reallocation When you are creating each component, you give an initial resource allocation for that  component. This allocation includes giving the component a certain amount of vCPU and  memory. By default, you cannot change the storage on some of the containers. The defaults  in the resource allocation are sufficient to run a successful blockchain network. Figure 2-29  on page 65 is a picture of the sample default resource allocation for a CA: Figure 2-29 sample default resource allocation for a CA: However, consider a scenario where you use Grafana ( https://grafana.com/ ) to monitor  your components and their resources. When you check Grafana, you notice that a certain  component could use more or less resources than what you originally allocated. If you want to  Chapter 2. Planning for installation  65