Table of Contents
- Market Categories
- Key Criteria Comparison
- GigaOm Radar
- Vendor Insights
- Analyst’s Take
- About Joep Piscaer
The adoption of cloud-native, container-based architectures and application modernization continues to fuel demand for persistent storage on Kubernetes platforms. Organizations understand that the benefits of cloud-native workloads in terms of performance, scalability, and portability are key enablers for achieving business goals.
Many enterprises are already running cloud-native workloads and understand the benefits of more agile and flexible architectures, including application portability that enables frictionless workload movement from the data center to the cloud, and even across clouds, providing greater flexibility and responsiveness to business requirements than legacy technologies do.
Data storage solutions for Kubernetes environments have evolved since our last report, especially in the realm of migration and mobility, as well as in maturing enterprise features for security, advanced data services, and enhanced developer experience.
A common pattern in the adoption of persistent storage solutions for Kubernetes is the reuse of existing enterprise storage solutions. This is considered a safe bet for the first couple of deployments, but it can’t cope with the sheer number of backend operations required by Kubernetes at scale. This limitation, together with the complexity involved in managing multicloud environments with traditional storage, encourages users to look for smarter and more efficient alternatives.
Compared to other types of storage systems, Kubernetes-native storage offers an environment that is more friendly to development operations (DevOps), helping to build a hardware stack that can be controlled by the operations team while enabling developers to allocate and monitor resources quickly, in a self-service fashion, when necessary. This is a major boon for enterprise IT organizations looking for the smartest way to evolve their processes and align them with the latest business and technology requirements.
Organizations can now consider more factors than ever before, including financial and business issues, when choosing where their applications and data should run—and they want the freedom to decide where that should be. The public cloud is known for its flexibility and agility, but on-premises infrastructures are still better in terms of efficiency, cost, and reliability. With widespread adoption across cloud, edge, and on-premises, Kubernetes is instrumental in executing the vision of portable, flexible, and agile hybrid cloud strategies, making applications and their data both portable and cloud-agnostic—for the most part. It needs the right integration with infrastructure layers—such as storage—to complement its still-maturing native support for stateful data storage.
It’s still a significant task to select and implement a Kubernetes storage solution for persistent data that makes the most of Kubernetes’s application mobility and data portability capabilities.
With Kubernetes now supporting business-critical applications and services, requirements have become more stringent. Scalability, performance, resilience, security, and other non-functional requirements are the order of the day, and Kubernetes needs to do it all to ensure a consistent level of throughput without service disruptions. These requirements drive the demand for enterprise-class stateful data services, solid security controls, mature multitenant performance management—like quality of service (QoS) and bandwidth throttling—and thorough alerting, reporting, and monitoring.
Lastly, enterprises do not want to be locked into any single vendor’s ecosystem as they reap the benefits of Kubernetes’s portable and agnostic promise, and they’re looking for a storage solution that works with feature parity across on-premises and cloud infrastructures.
This report focuses on cloud-native persistent storage solutions for Kubernetes. These are architectures specifically designed to address the needs of cloud-native applications without compromising on performance or scalability. They are usually not engineered to co-exist with other workload types, such as virtualization.
How to Read this Report
This GigaOm report is one of a series of documents that helps IT organizations assess competing solutions in the context of well-defined features and criteria. For a fuller understanding, consider reviewing the following reports:
Key Criteria report: A detailed market sector analysis that assesses the impact that key product features and criteria have on top-line solution characteristics—such as scalability, performance, and TCO—that drive purchase decisions.
GigaOm Radar report: A forward-looking analysis that plots the relative value and progression of vendor solutions along multiple axes based on strategy and execution. The Radar report includes a breakdown of each vendor’s offering in the sector.
Solution Profile: An in-depth vendor analysis that builds on the framework developed in the Key Criteria and Radar reports to assess a company’s engagement within a technology sector. This analysis includes forward-looking guidance around both strategy and product.