IBM Cloud Managed Istio vs. Percona Operator

It is a perfect application when you have multiple users and/or developers and you want to create rules and standards for access and the ability to change access levels. The reporting of usage is good, but adding more granularity into the metrics that have been used to measure are not specific enough. They provide detail but drilling into the detail would be more appropriate i.e. access to the baseline data.

Incentivized

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.

• Debug issues
• Monitoring
• allows many services form many different sources

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

• Still missing functionalities for a full usage as traffic director.

Incentivized

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

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.

Training and usage support available

Incentivized

Well documented, there was no need to contact support.

1) One-stop solution for all the complex network connectivity managed by [IBM Cloud Managed Istio]. 2) Nice dashboard to understand the flow. 3) Easy to troubleshoot the service if any one of the APIs is not responding. 4) We can integrate it with Azure Kubernetes service and other cloud provider Kubernetes services. 5) Monitoring the health of the pods can be easily configured and alerts can be triggered very accurately with this tool.

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.

• Management burden is reduced resulting in positive ROI.
• Application is being seamlessly instrumented with good impact on business.

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.