Percona Kubernetes Operators vs. Rafay

Production ready, robust DB solution built for Kubernetes envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional" MySQL and other clustering solutions. Also be sure to match it with proper k8s storage solutions.

Rafay is well suited for managing K8 deployments in on-prem deployments as well as AWS. Their support for GKE seems a bit limited.

Incentivized

• Easy and fast deployment.
• A reliable, fully automated, high-available db lifecycle management solution.
• Exaustive documentation.
• Production ready.

• 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.

• Seamless Single Sign-On Integration
• Use of a jumpstation to bootstrap a new EKS cluster deployment
• Some information in the UI does not auto populate
• UI can be enhanced a bit

Incentivized

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.

So far our experience with using Rafay's platform has been very positive.

Incentivized

Well documented, there was no need to contact support.

I have dealt with a lot of support organizations and am really glad to say that Rafay goes above and beyond expectations when it comes to supporting our teams.

Incentivized

For a long time we struggled finding a viable solution to migrate our existing db workloads inside Kubernetes. 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 MySQL 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.

No, we are very satisfied with the contract terms and pricing model and hope it does not change in the future.

Incentivized

• 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.