IBM® Storage Ceph® is a software-defined storage platform that consolidates block, file and object storage to help organizations eliminate data silos and deliver a cloud-like experience while retaining the cost benefits and data sovereignty advantages of on-premises IT.
N/A
Longhorn Block Storage
Score 10.0 out of 10
N/A
Longhorn is cloud native distributed block storage for Kubernetes, supported by Rancher Labs headquartered in Cupertino.
DevOps Architect for Containerization Platforms and Microservices
Chose Longhorn Block Storage
GlusterFS was first Persistent Storage solution used in our Kubernetes-based clusters. It is file-based what in some usages led us to many data corruptions. CEPH is object-based persistent storage which can be used as file-based Persistent Storage in Kubernetes. It is also is …
Large scale data storage: Red Hat Ceph Storage is designed to be highly scalable and can handle large amounts of data. It's well suited for organizations that need to store and manage large amounts of data, such as backups, images, videos, and other types of multimedia content.Cloud-based deployments: Red Hat Ceph Storage can provide object storage services for cloud-based applications such as SaaS and PaaS offerings. It is well suited for organizations that are looking to build their own cloud storage infrastructure or to use it as a storage backend for their cloud-based applications.High-performance computing: Red Hat Ceph Storage can be used to provide storage for high-performance computing (HPC) applications, such as scientific simulations and other types of compute-intensive workloads. It's well suited for organizations that need to store
Longhorn is performing well as storage for databases and in almost any solution that uses exclusive access to volumes (ReadWriteOnce in Kubernetes nomenclature). When write access is required from many clients (ReadWriteMany) Longhorn Block Storage covers its volumes with NFS (file-based) access. Longhorn Block Storage also is well fitted in every architecture where data security (snapshots, backups, multiple replicas) is more important than access speed (in terms on IOPS and MiB/s).
Highly resilient, almost every time we attempted to destroy the cluster it was able to recover from a failure. It struggled to when the nodes where down to about 30%(3 replicas on 10 nodes)
The cache tiering feature of Ceph is especially nice. We attached solid state disks and assigned them as the cache tier. Our sio benchmarks beat the our Netapp when we benchmarked it years ago (no traffic, clean disks) by a very wide margin.
Ceph effectively allows the admin to control the entire stack from top to bottom instead of being tied to any one storage vendor. The cluster can be decentralized and replicated across data centers if necessary although we didn't try that feature ourselves, it gave us some ideas for a disaster recovery solution. We really liked the idea that since we control the hardware and the software, we have infinite upgradability with off the shelf parts which is exactly what it was built for.
ReadWriteMany Longhorn volumes are still using NFS (file-based) protocol in the core.
Using iSCSI as main protocol instead of FC ties Longhorn to Ethernet-based LAN which is in most architectures much slower that FC-based SAN.
Longhorn could implement S3 as alternative access protocol to its volumes.
Backups, and snapshots configuration could be configured at each volume-level by administrators (maybe from additional CRD object?), because currently is configured at storage-class level which is not granular enough.
Longhorn is mature software defined storage solution that is still developed and receive new functionalities. From the beginning every Longhorn volume have multiple (at least two) replicas, can leverage manual or automatic snapshots and backup to external S3 volume. Longhorn provides nice and clear GUI for administrators, but also can be managed from CLI.
MongoDB offers better search ability compared to Red Hat Ceph Storage but it’s more optimized for large number of object while Red Hat Ceph Storage is preferred if you need to store binary data or large individual objects. To get acceptable search functionality you really need to compile Red Hat Ceph Storage with another database where the search metadata related to Red Hat Ceph Storage objects are stored.
GlusterFS was first Persistent Storage solution used in our Kubernetes-based clusters. It is file-based what in some usages led us to many data corruptions. CEPH is object-based persistent storage which can be used as file-based Persistent Storage in Kubernetes. It is also is much more resource-hungry than other solutions including Longhorn. Dell PowerScale (or Isilon) is a hardware-software solution, that provides volumes that can be accessed by file-based NFS and CIFS protocols. Recently was added access to its volumes with object-based S3 protocol. Longhorn is in the middle. It is block-based, it is build on industry standards like iSCSI, performs very well on 10Gbit or faster LAN and commodity hardware (or in virtual machines)
