# Node Architecture ## [**NODE LINK**](https://github.com/GRANDblockchain/cyclone_release) ## Node Architecture in the Cyclone System In its current implementation, a Cyclone node utilizes a full-fledged microservices architecture. Each microservice operates independently, and if desired, each can be deployed in a separate environment. Microservices communicate with each other either through sockets or HTTP protocols. The node comprises the following microservices: * Consensus Service: This microservice is responsible for coordinating the consensus mechanism among nodes, ensuring agreement on the validity of transactions and the state of the blockchain. * Storage Service: The storage microservice manages the storage and retrieval of blockchain data, maintaining the integrity and accessibility of the distributed ledger. * Cryptography Service: This microservice handles cryptographic operations such as signature verification, encryption, and decryption, ensuring the security and privacy of transactions and data. * P2P Microservice: Responsible for peer-to-peer communication, this microservice facilitates the exchange of transactions, blocks, and network-related information among nodes, ensuring the decentralization and resilience of the network. * VM Microservice: The VM microservice executes smart contracts written in various scripting languages, bytecode, or compiled binary formats. It provides an environment for contract execution and data manipulation within the Cyclone blockchain. Additionally, Cyclone implements the following auxiliary microservices: * CLI Microservice: The Command Line Interface (CLI) microservice offers a user-friendly interface for interacting with various aspects of the node's functionality, simplifying node management and operation. * Gateway Microservice: The gateway microservice acts as a bridge between external applications and the node's microservices, facilitating seamless integration and interaction with the Cyclone blockchain. It's worth noting that any microservice within the Cyclone node architecture can be rewritten if necessary, as long as it adheres to the established standards and can be redeployed without requiring a system-wide restart. This flexibility allows for iterative improvements and optimizations to individual components of the node architecture without disrupting the entire system's operation. Validators play a crucial role in ensuring the security and reliability of the network. They verify and confirm transactions sent to the Cyclone network, which includes authenticating transactions and ensuring they comply with the rules, protocols and [Consensus Mechanism](/overview/cyclone-chain/consensus-mechanism.md)of the blockchain. More about Cyclone Validators: ## [COT Token & Validators](/gamechanging/economics/cot-token-and-validators.md) --- # 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://docs.cyclonechain.com/develop/node-architecture.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.