Network Configurations

Every Network Configuration comes with a different configuration in terms of the number of Nodes and computational power. The following table outlines available resource limitations based on the provisioned node's size and will help you understand what constitutes a Network Configuration.

*The number of nodes mentioned above is the default number of nodes for each network size. It is recommended to have a total of at least 3 orderer nodes in the entire network for production deployments.

**The req/sec mentioned above are indicative numbers and the actual performance of a network depends on various factors like the number of organizations, channels, endorsement policies, the performance of chaincode, etc.

Learn more about Nodes: Nodes: Peer, Orderer & CA

Spydra allows users to add a custom number of nodes while creating Network, joining a Network, or later on from the Node page. It is recommended to have an odd number of Orderer nodes for consensus.

Why is it recommended to have an Odd number of Orderer nodes on a Network?

Only organizations that have a Network Admin role will be able to add Orderer Nodes. This can be used to limit which organizations should be able to participate in the network consensus.

Changing the Network Configuration will also affect your Organization's pricing. Please learn more about the pricing here. Pricing

How to Choose Network Configurations?

You can choose a Node Configuration based on your requirement and the limitations of the Network Configurations.

If you are still unsure about how to go about it, we recommend you choose the Network Configuration based on the below illustration.

  • Proof of Concepts / Testing - Small Networks

  • Startups / SMBs / Small-Medium scale projects - Medium Networks

  • Enterprises / Large Scale projects - Large Networks

For more information and guidance for choosing specific orderer and peer size and number, refer to Nodes: Peer, Orderer & CA.

Last updated