Likelihood to Recommend - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. K8s should be avoided - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills. Kubernetes is a good choice Read full review
Production ready, robust DB solution built for
envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional"
and other clustering solutions. Also be sure to match it with proper k8s storage solutions.
Read full review Pros Complex cluster management can be done with simple commands with strong authentication and authorization schemes Exhaustive documentation and open community smoothens the learning process As a user a few concepts like pod, deployment and service are sufficient to go a long way Read full review Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. Exaustive documentation. Production ready. Read full review Cons Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally. The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively. Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking. Read full review Some differences compared to "traditional" MySQL solution. Had some hard times trying to use it combined with pre-existing techs like WordPress, Magento, etc. The specific k8s environment features can have an impact on it, like the storage solutions offered by the cloud vendor. Read full review Usability
Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. It requires a bit of learning time for people new to operators ecosystem.
Read full review Support Rating
Well documented, there was no need to contact support.
Read full review Alternatives Considered
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
Read full review
For a long time we struggled finding a viable solution to migrate our existing db workloads inside
. Before "operators era" proper db workloads required manual management, of course that easily raised administrative overhead. Then the future started to be brighter with the introduction of operators and the "official" Oracle's
Operator, then Presslab's one, finally Percona's operator. Compared to other operators, the last one allowed us to ship production db workloads inside k8s.
Read full review Return on Investment Because of microservices, Kubernetes makes it easy to find the cost of each application easily. Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it. Read full review It allowed us to use k8s on our entire infrastructure. Decreased administrative overhead around our db services. As it is an open source technology, it cut down our db pricings. Read full review ScreenShots