Talking about storage instead of data misses the point.
There’s good reason why Gartner continuously publishes their ‘Hype Cycle’ reports about new technologies and/or new applications for those technologies. Vendor hype often drives buyer concern and focus. Such is the case when it comes supplying your cloud-based Kubernetes with stateful data.
A quick Google search on “persistent data for cloud-based Kubernetes,” and you’ll likely come away with either or both of these findings: One, the sky is falling, and your Kubernetes in the cloud just cannot get stateful data; Two, only storage vendors have the answers which, of course, means you need to buy more storage hardware or software. As a result, you end up stuck reading articles like this one or blog posts like this one that purport to clarify the ‘persistent data problem’, then present storage vendor solutions as the answer.
But, ‘storage’ isn’t even the real issue for Kubernetes in the cloud. Remember, the issue is persistent data. You’re not looking for storage for your apps. You’re looking for persistent data – data that your apps require to run properly when and where that data is needed.
And what’s the best way to make data accessible and persistent to Kubernetes in the cloud? It’s not any kind of solution from legacy storage vendors. You don’t need more and expensive storage deployments. You need persistent, dynamically delivered data that is just as dynamic as, and persistently accessible to, your containerized apps. To know how to get that, read on.
Use a Cloud-Native Data Orchestration Solution, Just Like Your K8s Container Orchestration
Cloud based data orchestration solutions, such as Kmesh SaaS, address the data management layer for containerized apps in a similar way that Kubernetes addresses the app management layer. Kmesh SaaS transforms centralized data (file system data, unstructured data, NoSQL data) into distributed data, operating over multiple clouds, countries, and edges as a single global namespace. However, it does so without ever replicating the data! That means no additional storage costs.
Rather than having to aggregate their data by moving it to a centralized location prior to usage, developers can leverage Kmesh SaaS to grant apps access to any data, in real time and as needed. The data may continue to reside in its original location.
Cloud Data Orchestration Goes Where Storage Solutions Cannot
Consider the use of Kmesh with Kubernetes in a popular “Edge Computing” use case – the connected car. A connected car can send data to an edge compute node during travel, and as the car travels further, it can send additional data to different edge compute nodes. That data transfer from the car, to the edge, and eventually to the car maker for analysis is fine for a stateless app. But, if the car sends messages to different edge compute nodes as it is moving, and those messages need to be synchronized in real-time to understand car health now, stateless Kubernetes cannot help. This is where Kmesh adds value. Kmesh synchronizes the data at each edge compute node (plus data from other sources) and informs the Kubernetes-managed apps so that they can perform real-time functions. An important part of the Kmesh functionality is its storage-agnostic architecture. Kmesh is merely a software layer, so it can grab data from any source, making all edge compute nodes easily connected.
Access Data Everywhere without Storing it Everywhere
Today, a transformation is taking place from centralized data lakes to distributed data ponds. That’s because data can no longer stay centralized for modern apps and edge apps to function as promised.
Kmesh makes distributed data ponds merely appear as a centralized data lake. What actually occurs in the background is that Kmesh makes a single global namespace for all the distributed data. It looks like a centralized data lake, but it is not duplicated. Metadata makes it happen, and metadata dictates how to move data around. The SaaS portion of Kmesh is a user dashboard where enterprise IT establishes policies about where data resides and to point users to certain data locations.
How Current Kubernetes Users Leverage Kmesh