Azure Kubernetes Service (AKS) vs. Percona Kubernetes Operators

At one instance, there was a fire in our data center and the backup power had some issues because of which the whole DC went down. I believe with AKS and the replication it's easier to handle such a situation. Also, the scenario would have been pretty transparent to the end-users.

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.

• Highly repeatable process
• Minimizes the amount of software to install
• Easily scale resources to meet demand

Incentivized

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

• Need to update cluster manually
• Policies cannot be updated for existing components
• if any change in policy every has to create cluster

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.

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

Well documented, there was no need to contact support.

The ability to create new instances (i.e. elastic provisioning) is probably the fastest with Azure Kubernetes Service compared to the alternatives that I have looked at. From a pricing perspective, Microsoft always seems to find a way to be more competitive in this area, and literally every other field they play in.

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.

• Positive impact in moving applications to cloud from the in-hose data center to save cost
• Sometimes got affected with some bugs on the AKS infrastructure but hasn't caused a big kios as our production footprint in AKS is not yet high

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.