> 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/microservices-architecture.md).
# Microservices Architecture
At the core of Teranode's innovative design is its **microservices architecture**, which fundamentally alters how blockchain nodes operate. Unlike traditional nodes that process transactions sequentially, Teranode's architecture allows for the parallelization of processes, enabling it to manage a significantly larger volume of transactions simultaneously. This is achieved by decomposing the node's functionalities into distinct services that can be independently scaled.
This architecture allows for horizontal scaling, meaning that as demand increases, additional servers can be deployed to enhance capacity. Each new server contributes approximately **90%** of the capacity of the previous one, resulting in a highly efficient scaling model that can adapt to varying transaction loads.
---
# 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/microservices-architecture.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.