Percona Kubernetes Operators vs. Vultr

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.

Vultr is best suited to deploy classic web applications, web services, and websites. It's well suited for mid-level traffic but has a wonderful option of expanding the disk storage, making it very well suited to run applications and services that need to consume a lot of data but don't need a lot of computing power. It may not be well suited to run applications that rely on a vast number of web services and require a vast number of data centers.

Incentivized

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

• Cloud Computing
• SSD VPS computing
• Access controlling
• Dashboard
• monitoring

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.

• Price
• Bandwidth
• Tiers (more)
• Remove redundancy. Why have 3 things with 1 CPU and 2 GB of RAM? Just let them pick intel or AMD at the end.

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.

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.

Vultr started out primarily as a VM-only provider, but has since expanded offerings and locations to be a serious alternative for a lot of businesses currently using a large, expensive cloud provider. Vultr may not be for everyone or every workload, but there are many businesses and individuals that are adding way too much complexity and cost to their projects by using large cloud platforms they do not really need. Update to review: Vultr's new Optimized Compute offerings are a game changer. They are designed to accommodate a more diverse or resource-intensive workload

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

• My Business achieved more Returns on Investment since the servers are more affordable and highly available than what I've used before.