> 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/leveraging-web-technologies-and-open-source.md). # Leveraging Web Technologies and Open Source Teranode's architecture is designed to leverage existing **web technologies** to enhance scalability and performance. The team focused on utilizing established communication protocols, such as **HTTP** and **REST APIs**, to facilitate data exchange between nodes. This approach allows for seamless integration with existing web infrastructure, drawing on decades of experience in scaling web applications. Additionally, Teranode embraces an **open-source** model, making its source code available on **GitHub**. This transparency fosters community engagement, enabling developers to review, optimize, and contribute to the codebase. The open-source nature of Teranode not only enhances its credibility but also aligns with the BSV blockchain's commitment to large-scale usability and compatibility with the original Bitcoin protocol. The collaborative efforts of the BSV Association and external developers have been instrumental in trialing and testing the software, ensuring that it meets the rigorous demands of a full blockchain system while maintaining the flexibility to adapt to future innovations. --- # 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/leveraging-web-technologies-and-open-source.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.