> For the complete documentation index, see [llms.txt](https://docs.nodeum.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nodeum.io/data-archiving/architecture.md).
# Architecture
Standalone and high-availability deployment models for Nodeum, including redundancy, heartbeat monitoring, and failover/fallback behavior.
***
### **Standalone System Overview**
This implementation is tailored to maximize the efficiency of a standalone x86 server, leveraging available hardware resources for scalable performance. The system is optimized to deliver robust internal hardware protection through multiple network connections and RAID disk controllers.
### **High Availability**
A High Availability (HA) cluster addresses system reliability by detecting hardware and software failures on the primary node. It automatically restarts Nodeum services on a backup node, removing the need for admin interventions. Nodeum clusters are designed to ensure redundancy and eliminate single points of failure. A heartbeat mechanism continuously monitors the health and status of each node. Metadata and configurations stored in databases and files are replicated across nodes, allowing seamless failover and fallback processes.
---
# 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://docs.nodeum.io/data-archiving/architecture.md?ask=&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.
