Minimal Configuration
[Table of Contents](https://github.com/dell-oss/Doradus/wiki/Doradus Administration: Table-of-Contents) | [Previous](https://github.com/dell-oss/Doradus/wiki/Basic Architecture) | [Next](https://github.com/dell-oss/Doradus/wiki/Two Node Configuration)
Deployment Guidelines: Minimal Configuration
Doradus uses the Cassandra NoSQL database engine for persistence, scalability, and availability. Compared to traditional relational database systems, which scale vertically, NoSQL databases such as Cassandra scale horizontally. This means that they do not require high-end servers, SAN storage, RAID configurations, and fiber channel but instead utilize a cluster of low cost, "shared nothing" servers.
Each server within a cluster is referred to a node. Each node adds processing capabilities to the cluster via local processes, and it adds storage capacity via locally-attached disk. For smaller deployments and testing environments, a single node can be used that runs one instance each of the Doradus Server and Cassandra Server. For a minimal level of protection, the data and log files should reside on redundant disks (e.g., RAID level 1). This is depicted below:
Figure 2 – Single Node Configuration
One or more application processes are assumed to reside on separate, network-near servers. In many cases, the application server process can also reside on the same node.