DAOS vs Longhorn
DAOS
daos.ioLonghorn
longhorn.ioSide by side
| Figure | DAOS | Longhorn |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Software-Defined Storage Software | 7.7 (#16) | 7.8 (#14) |
| Spec score · Storage Replication Software | 7.6 (#13) | 7.7 (#11) |
| Security | DAOS supports access control lists on pools and individual containers. | Longhorn supports mTLS to secure and encrypt gRPC communication between its control plane and data plane, but mTLS is disabled by default. |
Plans
In their own words
Longhorn
Longhorn is a free, open-source distributed block storage system for Kubernetes. It replicates storage across nodes and data centers to increase availability, with V1 replicated, V2 replicated and V2 sharded with erasure coding volume types. Teams can schedule recurring snapshots and backups to NFS or S3-compatible secondary storage, and create disaster recovery volumes for recovery in a second Kubernetes cluster. A GUI dashboard is included, and the management UI is described as free. The software stack can be upgraded without disrupting running storage volumes. Installation options include kubectl, Helm, Fleet, Flux and ArgoCD. Longhorn supports mTLS for securing and encrypting gRPC communication between its control and data planes, but mTLS is disabled by default. Components need root access with privileged permissions for volume operations and management. Backups require an NFSv4 client, while ReadWriteMany volumes require NFSv4.1. Longhorn runs on Linux and supports API, web and self-hosted use. It is a CNCF incubating project; SUSE Storage is described as a Longhorn-based distribution with additional support, security, lifecycle management and certified integrations.