Category: Software, Business, Data, Kubernetes, containerization
The Kubernetes orchestrator relies on volumes-abstracted storage resources - that help to save and share data between ephemeral containers.
In Kubernetes, shared storage is typically achieved by mounting volumes and connecting to an external filesystem or block storage solution.
Because CAS is deployed per workload or per cluster, it also eliminates the cross workload and cluster blast radius of traditional shared storage.
Following are a few similarities and differences between CAS and Traditional Shared Storage: Designed in Kubernetes, CAS enables agility, granularity and linear scalability, making it a favourite for cloud-native applications. Traditional shared storage offers a mature stack of storage technology that mainly falls short in persisting storage for stateful applications due to the inherent lack of linear scalability.
In Kubernetes, shared storage is typically achieved by mounting volumes and connecting to an external filesystem or block storage solution.
Because CAS is deployed per workload or per cluster, it also eliminates the cross workload and cluster blast radius of traditional shared storage.
Following are a few similarities and differences between CAS and Traditional Shared Storage: Designed in Kubernetes, CAS enables agility, granularity and linear scalability, making it a favourite for cloud-native applications. Traditional shared storage offers a mature stack of storage technology that mainly falls short in persisting storage for stateful applications due to the inherent lack of linear scalability.
Related Articles
Community Partners
DevOps Careers