Skip to main content
TrustRadius
Longhorn Block Storage

Longhorn Block Storage

Overview

What is Longhorn Block Storage?

Longhorn is cloud native distributed block storage for Kubernetes, supported by Rancher Labs headquartered in Cupertino.

Read more
Recent Reviews
Read all reviews

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Longhorn Block Storage?

Longhorn is cloud native distributed block storage for Kubernetes, supported by Rancher Labs headquartered in Cupertino.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

3 people also want pricing

Alternatives Pricing

What is Vultr?

Vultr is an independent cloud computing platform on a mission to provide businesses and developers around the world with unrivaled ease of use, price-to-performance, and global reach.

Return to navigation

Product Details

What is Longhorn Block Storage?

Longhorn Block Storage Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(2)

Attribute Ratings

Reviews

(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
Szymon Madej | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use Longhorn Block Storage as primary Persistent Storage in our Kubernetes platform based on Rancher. Before changing to Longhorn we used file-based solutions NFS and GlusterFS, which were incapable of hosting databases especially NoSQL blob storage used in ElasticSearch, Redis, ETCD, RabbitMQ and similar products, what resulted in common data corruption issues. Longhorn Block Storage gave us what we needed: secure, replicated and reasonably fast persistent storage.
  • Leverages industry standard protocol (iSCSI)
  • Is block-based storage instead of file-based
  • Is truly software defined storage (SDS)
  • Can use commodity hardware to build redundant SDS
  • Is open-source software
  • Is one of the CNCF projects
  • Provides enterprise functionalities like snapshots or backups
  • 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 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).
  • Longhorn is fully open source. One can try and/or use Longhorn for free even in enterprise and buy subscriptions only for environments that must be fully supported. We started with Longhorn in our lab environment and followed on through reference platform to non-production and production environments.
  • Longhorn subscriptions are not cheap, but its biggest advantage is that price-to-functionality ratio is very reasonable.
  • We have volumes with hundreds of gigabytes of data and these on Longhorn perform well in solutions where file-based GlusterFS volumes were corrupting data.
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.
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).
Score 10 out of 10
Vetted Review
Verified User
We use Longhorn Block Storage for Rancher-managed Kubernetes cluster storage requirements. It is easily installed from Rancher web GUI with a few mouse clicks. Longhorn Block Storage solves our problem with read-write many (RWX) volumes. Many solutions provide only read-write once (RWO). Longhorn Block Storage, in the beginning, also did not support RWX, but the support was added in v1.1.0. Also, it's easy to make scheduled or on-demand volume snapshots using Longhorn web GUI. We use it to schedule regular volume snapshots and, in case of data corruption or other disasters, restore data back to volumes. Snapshots are lightning fast because Longhorn Block Storage is built on block storage.
  • Creates read-write many (RWX) volumes
  • Longhorn Block Storage is an easy to deploy solution
  • Scheduled and on-demand volume snapshots can be created using web GUI
  • Volume backups can be stored offsite on any S3 compatible storage solution
  • Backups and snapshots can be restored using web GUI
  • Version to version upgrades takes more expertise to do than initial deployment
  • If something goes wrong, you will need a help from support
  • Longhorn Block Storage speed is slightly slower than local disk storage speed
Longhorn Block Storage is well suited for most Kubernetes workloads where data storage is required, but when very high storage speed is essential, Longhorn Block Storage might not be the best solution. For those rare situations, we use local storage mounts. Longhorn Block Storage's ability to easily create/restore volume snapshots is a very frequently used feature among our dev teams because they can easily play multiple scenarios with the same data - modify data, restore it and modify it again.
  • Longhorn Block Storage is an easy to deploy solution
  • Easy to create/restore volume snapshots
  • Supports read-write many volume type
  • It has provided a highly available storage solution for almost all our Kubernetes deployments
  • We can deploy new app versions with peace in mind because we have working data backups
  • Application development is faster because devs can play with data and easily restore it when needed
Return to navigation