> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/essentials-of-teranode-microservices-and-infrastructure-solutions/infrastructure-requirements.md).

# Infrastructure Requirements

The infrastructure required to support Teranode's ambitious transaction processing capabilities is substantial. The development team utilized **AWS (Amazon Web Services)** to deploy nodes, each configured with:

* **96 CPUs**
* **512 GB of RAM**
* **NVMe disks for high-speed data access**

To achieve the desired performance, the team operated **20 machines per node**, resulting in a total of **3,000 CPUs** and approximately **15 terabytes of RAM** across six nodes. This configuration enabled the system to reach a peak performance of **1.1 million transactions per second**.

However, the cost of maintaining such infrastructure is significant, with each node costing around **$250,000 per month**. The decision to limit performance to 1.1 million TPS was primarily driven by cost considerations rather than technical limitations, highlighting the potential for even greater scalability in the future.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/essentials-of-teranode-microservices-and-infrastructure-solutions/infrastructure-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.