Learn how data center nodes ensure scalability, performance, and resilience.
The nodes that make iov42 networks are data centers
Node operators must have access to a data center
Conventional node architecture:
Any device that has the connectivity, storage capacity, and processing ability to support a DLT network, e.g. laptops, PCs, specialist farms of custom hardware
More nodes within a DLT network improve resilience against system-threatening events
Problems with conventional node architecture:
Performance of the blockchain is limited by the computing and storage capacity of one node
Networks comprising hundreds or even thousands of nodes necessitate slow consensus algorithms to prevent unwanted interventions
Because the traditional blockchain model of a single device node is not scalable, iov42 has reimagined the structure of the node.
iov42 node architecture:
Nodes are data centers that leverage distributed computing and cloud supporting technologies
Use of Docker and Kubernetes facilitates deployment of the iov42 network to different cloud providers and traditional data centers
Benefits of iov42 node architecture:
The ability to add resources as needed as the data across the system increases
A data center node model limits the number of possible node operators within an iov42 network. Not only does this enhance the performance of the system, it also means that networks will be made up of recognized entities that are known to each other. Deliberate network formation increases the system’s flexibility to address issues of governance, industry-specific security concerns, and data locality.
To understand how iov42 nodes connect with one another to form a network, read about iov42’s zoned architecture here.