What determines database performance?
In databases the biggest bottleneck is disk latency. NVMe disks are far faster than SATA disks in random reads and writes; that is why this page lists only servers with NVMe disks.
The second factor is memory: when frequently used data is kept in RAM, disk access falls and queries speed up. Error-correcting (ECC) memory reduces the risk of data corruption in long-running databases; if present, it is stated in the details.
Backup and reliability
On two-disk servers you can mirror the disks with RAID 1 for protection against a single disk failure. Still, do not neglect regular backups and, where possible, replication to a second server.
You can run databases such as MySQL, MariaDB, PostgreSQL, Redis and MongoDB on Linux. For setup and tuning support see our management packages.
Common mistakes when choosing
Ignoring the disk: two servers with the same RAM can differ greatly in database performance between NVMe and SATA.
Trusting a single disk: without RAID or replication a single disk is a single point of failure.
Not anticipating growth: as data volume grows, memory and disk needs grow too; think about moving up a model from the start.