Points, the loyalty currency platform provider makes the move from AWS to on-premises Kubernetes, leveraging the operational benefits of Quobyte software storage.
Storage shouldn’t be an afterthought in container contexts
Containers are an integral part of today’s DevOps for reducing cost and complexity and enabling the rapid testing and deploying of applications. But once you’re lifting your application containers into production, you need an answer to the question of what to do with their data.
Containers deliver great flexibility – if one crashes, just fire up the next. Its data, however, will perish along with it unless you have a proper storage solution in place – a solution that’s up to par with container flexibility and integrates with the current container management schedulers.
Quobyte’s distributed file system is up to the task – it not only provides container-native storage, but is designed with scalability in mind to cope with the requirements of modern enterprise IT infrastructures and their workloads.
Seamlessly integrate Quobyte with your container ecosystem
The new Quobyte Operator for Kubernetes installs a container storage cluster for Kubernetes within minutes. Use it for greatest setup simplicity! Quobyte also has a volume plugin directly integrated with Kubernetes at the ready. It enables a cluster-wide storage mount on Kubernetes and simplifies storage management and operations.
We have created Docker images to simplify Quobyte deployment in container infrastructures. They come with your Quobyte distribution. A Quobyte volume plugin for Docker is also available.
In order to deploy Quobyte on a Mesos cluster, we’ve created a dedicated Quobyte-Mesos framework, available on GitHub. The Quobyte Mesos Framework is certified for Mesosphere’s DC/OS, but can also be used to deploy Quobyte on independent Apache Mesos clusters.
With its POSIX-compatible file system, Quobyte provides restrictions-free storage. Any application is independent of the limits that local storage sets. One major benefit is fault tolerance: when the current host dies, the application can be started on a different server and still access its data.
In a distributed environment, this can get you into troubled waters: a scheduler might erroneously suspect a host to be dead and reschedule the application on a different host. Even though the original instance is still alive, another application instance jumps in and the two of them start working on the same data. Data corruption ensues.
Starting with version 1.2, Quobyte has the solution: it transparently manages fault-tolerant locks for any file access and thereby ensures that only one application instance has access to the data. You can just deploy your application and don’t need to take measures for fault tolerance. Quobyte takes care of it on the storage side, eliminating further overhead.