Multi-node architecture
Multi-node architecture
A multi-domain system can be deployed in a multi-node configuration, where each unit represents a separate physical or virtual device with its own set of domains. This architecture enhances the system's flexibility, scalability, and fault tolerance.
Essential aspects of multi-node architecture
- Node Independence:
Each node operates autonomously and can perform tasks independently from other nodes. Both centralized and decentralized update coordination are possible. - Flexible Component Distribution:
System components (services, user applications, update managers, etc.) can be distributed across different domains depending on performance, security, and resource availability requirements. - Centralized or Distributed Management:
System updates and management can be handled either by a central System Manager (SM) that has information about all nodes, or by local SMs on each node that communicate with each other.
Benefits of Multi-node Configuration
- Increased Fault Tolerance — failure of a single node does not disrupt the operation of the entire system.
- Scalability — adding new nodes increases resources and expands functionality.
- Task Isolation — services and workloads can be separated across nodes, improving security and stability.
Main components
For a detailed overview of the architecture, refer to the AOS Core Architecture documentation AOS Core Architecture documentation.
Build multi-node
You can try building a multi-node virtual machine using the instructions in the meta-aos-vm repository.