> 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/redesign-necessity.md).
# Redesign Necessity
The necessity for a complete redesign of node software stems from the inherent limitations of existing systems, which are primarily based on the original Bitcoin model established in 2009. Traditional node software operates as a **monolithic** entity, encapsulating all functionalities—transaction validation, network communication, and block processing—within a single binary. This design leads to significant performance bottlenecks, particularly evident in Bitcoin's transaction processing limit of just **seven transactions per second** due to block size restrictions and locking contention issues.
The Teranode development team recognized that the existing model's limitations were **not merely technical but also architectural**. By returning to the drawing board, they sought to dismantle the monolithic structure and create a more efficient, scalable solution that could handle the demands of modern blockchain applications, particularly in enterprise-level environments where high transaction volumes are commonplace.
---
# 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/redesign-necessity.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.
