# 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: 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:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/essentials-of-teranode-microservices-and-infrastructure-solutions/redesign-necessity.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.