Spydra Docs
For Developers
Spydra Platform
Spydra Platform
  • GETTING STARTED
    • Introduction
    • Why Spydra?
    • Blockchain fundamentals
      • Why Blockchain?
      • Private Blockchain
      • Public Chain
    • 🎧Getting started with a Private Network
      • Creating an account
      • Creating an organization
      • Creating a Network
      • Apps
    • 🔊Getting started with a Token Store on Public Chain
      • Token store
      • Customise token store front
      • List a real world asset and issue tokens
      • Manage token lifecycle
    • Intro to Hyperledger Fabric
  • Products Overview
    • 🎧Private Network
      • Organizations
        • Users and Organizations
        • Organisation Hosting - Spydra Hosted and BYOC
        • Organization Statuses
        • Organization Roles & Permissions
        • Organization Dashboard
        • Organization Entities
      • Networks
        • Network Statuses
        • Network Roles & Permissions
        • Network Configurations
        • Mandatory Card Addition
        • Nodes: Peer, Orderer & CA
        • Network Hosting Type
        • Network Dashboard
        • Network Operations
        • Nodes
      • Channels
      • Apps
        • Pre-Configured Apps
        • Custom Apps
      • Asset Tokenization
        • Use cases
        • Asset types
        • References
        • Asset Owners
        • Permissions
      • Tokens & Vault
      • Listeners
        • Network Listeners
        • App Listeners
        • Token Listeners
      • Workflow Builder
      • Oracles
      • GraphQL
      • Block Explorer
      • IPFS
      • Fabric Debug Plugin
    • 🔊Public Chain
      • Token Store
      • Tokenize Real World Assets
      • Tokenomics: Token & Token Sale
      • Trade & Payout
  • How to
    • 🎧Private Network
      • Account
        • Create an Account
        • Edit Profile details
        • Update email & Password
        • Forgot password
        • Google OAuth Signup - Update Email & Password
        • Deactivating or deleting your account?
      • Organizations
        • Create an Organization
        • Create & Manage BYOC Hosting
        • Invite members to an organisation
        • Edit Organization details
        • Manage Org members
        • Leave an Organization
        • Update Organization member roles
        • Pay Organisation Invoice
        • Update Billing Address
        • View Invoices
        • Organization Dashboard
        • Delete an Organisation
      • Networks
        • Create a Network
        • Advance Settings: Key Vault Store
        • View and edit Network details
          • Update Permissions for Network Members
          • Update Network Configuration
          • Update Key Vault
          • Manage API Keys
          • Delete a network
        • Inviting an organisation to a Network
        • Network Roles & Permissions
        • Joining a Network
        • Network Dashboard
      • Apps
        • Explore Apps
        • Deploy App
          • Deploying Asset Tokenization App
        • Manage Apps
        • Application Dashboard
      • Channels
        • Creating a Channel
        • Create a Consensus Policy
        • Update Channel
        • Channel Members
        • Delete channel
      • Nodes
        • Create Node
        • Node Dashboard
        • Delete Node
      • Pre-configured Apps
        • Deploy Asset Tokenization App
        • Asset Data
      • Custom Apps
        • Deploy Custom Chaincode
        • Chaincode as external service
        • Supported File Formats - ZIP format
        • Building in Binary format
          • Golang - Binary Format
          • Java Jar files
        • Chaincode Logs
      • Workflow
        • Triggers
        • Condition
        • Read
        • Actions
        • End
        • Variables & Identifiers
        • Calculations & Formulas
      • Oracles
        • Create an Oracle
        • Oracle with Asset tokenisation
        • Oracle with Custom Chaincode
      • Listeners
        • Create a Listener
        • Manage Listeners
    • 🔊Public Chain
      • Account
        • Create an Account
        • Edit Profile details
        • Update email & Password
        • Forgot password
        • Google OAuth Signup - Update Email & Password
        • Deactivating or deleting your account?
      • Token Store
        • Create a Token Store
        • Design Store Front
        • Custom Domain Hosting
        • Google Analytics Integration
        • Create & Manage Store Users
          • Store User KYC
        • Accreditation Management
        • Store Payments
        • Token Store Customers
      • Tokenise a Real World Asset
        • Real Estate
        • Other Asset Categories
      • Create a token
        • Define your token
        • Investor & Buyback Settings
        • Configure token returns & payouts
        • Create token sale
      • Additional Configurations
        • Create a Document Workflow
      • Publish Asset
      • Tokenise on TestNet
        • Polygon Amoy
      • Manage Token lifecycle
        • Returns & Payouts
          • Initiate an equity payout
          • Authorise Debt Payouts
          • View all payouts
        • View token investors
        • View token transactions
        • View signed documents
        • View/ Create a token sale
        • Post Token Updates
        • Update Price
        • Buyback Requests
  • Billing & Pricing
    • Pricing
    • Billing
      • Opt-in Billing
      • Opt-out Billing
    • Adding a Card & Autopay
    • Invoice Payments
    • Billing forecast
    • Unpaid Invoices
    • Credits
  • Developers
    • API Reference
      • Asset Tokenization
        • REST API
        • Testing REST API
        • GraphQL
          • Quickstart
          • Simple queries
          • Nested object queries
          • Complex queries
          • Aggregate queries
          • Operators
          • Built-in attributes
          • Pagination
      • Custom Chaincode
        • REST API
        • Testing REST API
        • GraphQL
          • Quickstart
          • Simple queries
          • Complex queries
          • Operators
          • Pagination
      • Token Store (Public Chain)
        • Token Issuer
        • Investor
      • IPFS
    • Developer Tools
      • Monitoring [Coming Soon]
    • API Key
  • Support
    • FAQs
    • My account is banned [D]
    • Why is it recommended to have an Odd number of Orderer nodes on a Network?
    • Support
  • Others
    • Glossary
  • Policies
    • Terms & Conditions
    • Privacy Policies
    • Open Spydra
Powered by GitBook
On this page
  • Orderer Nodes
  • Peer Nodes
  • CA Nodes

Was this helpful?

  1. Products Overview
  2. Private Network
  3. Networks

Nodes: Peer, Orderer & CA

PreviousMandatory Card AdditionNextNetwork Hosting Type

Last updated 9 months ago

Was this helpful?

Nodes play a crucial role in maintaining the integrity and security of the blockchain network. They work together to ensure that transactions are processed accurately and that the blockchain remains tamper-resistant.

There are 3 types of Nodes in a Hyperledger Fabric network: Orderer, Peer and Certificate Authority Nodes

Orderer Nodes

The orderer nodes are responsible for maintaining the order and consistency of transactions on the blockchain. They ensure that all transactions are recorded in the correct order and that there are no conflicts between them. Spydra supports the protocol which is the de-facto implementation of ordering service for Fabric v2.x networks.

Guidance on choosing orderer node size and number:

Every pre-configured network size provided by Spdra has a default size and number for the orderer nodes. You can change the number of orderer nodes while creating or joining a network.

  • All organizations need not deploy orderer nodes. Organizations that want to be part of the blockchain network consensus process should deploy orderer nodes.

  • The total number of orderers in the network should be an odd number as this is recommended for the Raft protocol.

  • Raft provides Crash Fault Tolerance (CFT). Having more number of nodes improve resiliency as more nodes can be lost and the ordering service can still be functional. A five node cluster, for example, can tolerate two down nodes, while a seven node cluster can tolerate three down nodes.

  • However, more nodes mean a larger communication overhead, which could eventually slow the network. Raft clusters of more than a few dozen nodes begin to see noticeable performance degradation.

  • Adding more number of nodes does not help with improving performance as orderer nodes are not load balanced. Choosing a higher size for the node does improve performance.

  • Clusters of three, five, seven, or nine orderer nodes in a network are the most popular.

  • For additional information on choosing orderer nodes, refer .

Peer Nodes

The peer nodes are responsible for executing transactions, maintaining the ledger, and participating in the consensus process. They communicate with other peer nodes to validate transactions and reach a consensus on the state of the ledger.

Guidance on choosing peer node size and number:

Every pre-configured network size provided by Spdra has a default size and number for the peer nodes. You can change the number of peer nodes while creating or joining a network.

  • The size and number of the peer nodes have a direct bearing on the performance of the network.

  • Peer nodes are load balanced. So, increasing the size and number of nodes generally improves performance.

CA Nodes

The Hyperledger Fabric Certificate Authority (CA) node is responsible for managing the digital certificates and identities of network participants. It uses a Public Key Infrastructure (PKI) system to issue and manage digital certificates that are used to authenticate and authorize network participants.

Spydra provides a CA node for each organization by default and nothing additional needs to be done to enable this. The certificates and related keys are securely stored in a dedicated Hashicorp vault that is provisioned for each organization.

For additional guidance on choosing peer nodes, refer .

🎧
Raft
here
here