Longhorn Block Storage vs. StorPool

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.

Storpool performs well on block level (and that is what we use it for). It is not yet supporting a kind of distributed filesystem or object storage - a filesystem layer needs to be built on top of it.

• 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

• Distributed Storage array with very high throughput in terms of reading & write operations.
• Horizontal scaling without much complexity of management.
• Easily integrate with OpenStack cloud.
• Doesn't depend on proprietary hardware, integrates with commodity hardware.

• 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

• Graphical interface is for monitoring and stats, but not for operations.

We made a very careful selection of our storage vendor and solution. After researching the newest technologies, our team decided to deploy a software-defined storage solution from StorPool.

• 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

• We have not calculated precise ROI. We focused on getting the best solution at a reasonable price, based on market research. Initially, we didn’t need a lot of capacity, so we invested in servers and network, which could handle several times more capacity, but bought smaller drives to keep the investment low. We achieved a starting price of $3.2/GB usable and $1.4/GB logical. Later we expanded the capacity by adding more drives to the system. Currently, the system has a price of approximately $2.3/GB usable and $0.99/GB logical and a price of $0.09/IOPS.