MySQL on a PaaS vs a Virtual Machine – A Comparative Cost Study

Author: Justin Campbell

In the world of cloud transformation, the debate of hosting database systems such as MySQL on a Platform as a Service (PaaS) or a Virtual Machine (VM) under the Infrastructure as a Service (IaaS) model is always a hot topic. This article aims to explore the functionalities and operational benefits of each avenue and shine a light on their cost implications.

Understanding PaaS and IaaS

Before we delve into the numbers, let's quickly outline what each model entails:

1. PaaS (Platform as a Service): This cloud computing model offers both hardware and software tools over the Internet. It aids application development by providing an environment with everything needed to develop, test, and deploy applications.
2. IaaS (Infrastructure as a Service): IaaS delivers computer infrastructure on an outsourced basis to support enterprise operations. In our case, we are looking at VM as the specific service under the IaaS umbrella.

Costs of MySQL on PaaS vs IaaS (VM)

Looking at the cost structure, there is a noticeable difference between the two models.

For an IaaS solution:

• Monthly cost: $227.61
• Annual cost: $2,731.32

For a PaaS solution:

• Monthly cost: $310.26
• Annual cost: $3,723.12

All costs are based on real-world examples.

At first glance, it's clear that the PaaS solution seems more expensive. However, the cost comparison is more than just direct prices; we should also consider the indirect costs and value each solution brings to your organization.

To give you insight into the IaaS solution's underlying configuration, the stack it is compared with is 2 x Linux virtual machines, 2vcpu 8GB memory running in two different zones within the cloud, and an STD SSD drive with redundant storage replication and backups. I also included support in the form of a Dev/Ops-type cost per month for the IaaS solution to manage the stack.

Cost Efficiency of PaaS

Although PaaS's direct costs are higher, its value could lead to indirect cost savings. For instance, PaaS solutions can significantly cut down on the manpower and time needed for management and maintenance. PaaS solutions often include features like automated backups, updates, and scalability, which could add to your costs if managed manually in an IaaS scenario.

Cost Considerations for IaaS (VM)

With IaaS, the initial direct costs are lower. However, running MySQL on a VM requires more management and maintenance, from the operating system to the application layers. This could translate into higher manpower costs, potentially resulting in higher indirect costs over time.

Moreover, the on-demand scalability of PaaS could result in lower costs in the long term compared to VM, especially for businesses expecting rapid growth. Scaling a VM-based MySQL database may require more resources, driving up costs.

Conclusion: PaaS or VM – Which is More Cost-Effective?

The decision largely depends on your specific needs. PaaS, while having higher indirect costs, provides added value that could lead to significant indirect cost savings, making it a strong candidate for businesses looking for ease of use and scalability. On the other hand, VM (under IaaS) might be a more suitable choice for those prioritizing lower direct costs and requiring higher levels of customization and control.

One consideration that might be needed to be included in any decision-making process is the volume of database servers required; it could potentially be that an IaaS solution might be the more cost-effective longer term to host more database systems compared to PaaS. It might be possible to build a database shared services using IaaS components that serve your need more technically and cost-efficiently.

When making your choice, it's important to take into account both the direct and indirect costs, assessing the long-term value provided by each solution.

Thank you for joining me in this exploration of database management cost structures. Feel free to reach out with any questions or discussions.