Oracle MySQL Cloud Service vs. Percona Operator

It is very scalable and it gives us backup for everything. Because of this feature, we (as a developer) can do any R&D if required. It is very stable so we can get any type of help. It has a recovery feature also which we used recently for my project. It is very easy to recover.

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.

• Oracle database has ability to store large scale of data.
• It can support any kind of scenario with any label of system.
• Encryption and security is the key features of Oracle database 12c.

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

• It has some issues [when] performing local unit testing in personal edition.
• It is costly if we will go for cloud.
• Need license for some features.

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

Well documented, there was no need to contact support.

It has the most stable database. It smoothly supports [a] huge [amount of] data. Security-wise it is best among them. It is a very large community and has well-defined documentation, which can support [during the] implementation of the Oracle database. We can easily scale up servers whenever [we] change our requirements. Oracle12c is best for large-scale projects like banking and retails.

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.

• It has ability to handle [a] huge [amount of] data and give [the] best performance
• Easy to write PL/SQA queries
• Secure and encryption option

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