# Horizontal Scale Horizontal scalability, often referred to as *scaling out*, is a method of increasing a system's capacity and performance by adding more individual machines or nodes to the existing infrastructure. This is in contrast to *vertical scalability* (scaling up), which involves enhancing the power of a single machine by adding more CPU, RAM, or storage. The core advantage of horizontal scalability (in any given system) is that it's theoretically limitless. You can always add another machine to distribute the workload, whereas a single machine's capacity for upgrades (vertical scaling) will eventually hit its physical limits. Horizontal scaling also offers increased resilience and fault tolerance, as the failure of one node does not necessarily bring down the entire system; others can pick up the slack. ## How IronWeave is Capable of Horizontal Scalability IronWeave is inherently capable of horizontal scalability because of its fundamental architectural design: the multi-blockchain fabric. Unlike monolithic blockchains that operate as a single shared ledger, IronWeave establishes a decentralized network where: * **Every entity has its own chain(s)**: Each user, device, application, or AI agent on IronWeave possesses its own independent blockchain(s). These individual chains are the primary locus of activity for that entity. * **Interactions are atomic and independent:** When two or more entities interact (e.g., sending a message, sharing a file), they don't submit data to a global and public ledger. Instead, they collaboratively create a shared block that is an independently encrypted unit of data, for each specific interaction. This design means that IronWeave isn't trying to squeeze all global interactions through a single pipeline. Instead, it allows for a vast number of parallel, independent interactions. ## How IronWeave Achieves Horizontal Scalability IronWeave achieves horizontal scalability through the following mechanisms: * **Parallel Block Creation:** This is a critical architectural mechanism for IronWeave, as described in the [previous section](/scalability/parallel-block-creation.md). * **Decentralized By Nature:** The IronWeave fabric is a decentralized network of independent chains. As more users or entities join the network, they bring (create) their own chains, effectively adding more "processing lanes" to the overall system (or using the phone network analogy, the add their new phone line to the fabric). This means that the fabric's capacity grows with its adoption, without needing a centralized authority to manage or expand a single server or blockchain. * **No Global Consensus for Every Transaction:** In monolithic blockchains, every transaction generally requires some form of global consensus (e.g., Proof of Work, Proof of Stake) to be aggregated into the next available block, then added to the single chain. This process is time-consuming and resource-intensive. IronWeave's model removes the need for constant global consensus because interactions are localized to the participating chains. State is synchronized on a per-interaction basis (whenever a shared block is created), and global consensus of all chains is obviated. Double-spend is prevented by locking a spending chain, validating available balance, and anchoring any attempted spends with a massive three-dimensional array of hashes. While global consensus mechanisms ensure the fabric's integrity (described in subsequent sections), individual interaction finality is near-instantaneous due to direct chain updates. * **Unscannable Privacy as an Enabler:** IronWeave's *unscannable privacy* isn't just a feature; it's fundamental to its scalability. Because data is private by default and confined to involved parties, the network doesn't need to broadcast and process every piece of data globally for validation or auditing. This dramatically reduces the computational load and network traffic compared to public-by-default blockchains. * **Use of Zones to expand the Fabric**: IronWeave uses the concept of Zones to create expandable areas of the fabric, implementing its architecture of horizontal scalability. This is similar to how DNS (the Domain Name System) provides its horizontal scalability, yet allows connections from any Internet device to any other. IronWeave Zones are collections of validators and chains. Similar to how DNS validates queries for name resolution in each zone for which a DNS server is authoritative, in IronWeave Zones, participating validators are authoritative for their Zone and validate block requests (with consensus from others) for their Zone. Zones are described in more detail in another article. ## Summary of Horizontal Scale in IronWeave By disaggregating the concept of a global ledger into a vast network of independent yet interconnected private chains, IronWeave effectively scales out its capacity by adding more independent, parallel interacting units (individual chains and their blocks). This allows IronWeave to disaggregate at an architectural level, to handle millions of transactions per second, far exceeding the throughput of traditional monolithic blockchain architectures. So **horizontal scale** means that block creation, such as a payment or swap or contract or AI agent activity, can be created and validated in a distributed and decentralized manner, across IronWeave Zones and independent of a central monolithic blockchain. This is possible because each block is an independent interaction, with decentralized validation. Next, we describe how decentralized consensus works in IronWeave. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ironweave.io/scalability/horizontal-scale.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.