> 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/shared-infrastructure-and-storage.md).
# Shared Infrastructure and Storage
To facilitate communication between the various microservices, Teranode relies on a **shared infrastructure** that utilizes proven technologies for data storage and management. The system employs a combination of **network file storage** and **cloud-based solutions**, such as **Amazon S3 (Simple Storage Service)**, to handle the vast amounts of data generated by high transaction volumes.
The architecture includes:
* **Merkle Subtrees**: A hierarchical structure that allows for efficient proof generation for large blocks, enhancing the verification process.
* **PostgreSQL Database**: Used to track block headers and metadata, ensuring that the system maintains a comprehensive record of all transactions and their statuses.
By leveraging established technologies, Teranode **minimizes complexity while maximizing performance**, allowing it to efficiently process transactions at scale.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/essentials-of-teranode-microservices-and-infrastructure-solutions/shared-infrastructure-and-storage.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.