해리슨 블로그

GCP DB Instance Pricing Comparison (Cloud SQL vs AlloyDB)

Created: 2024-06-15

Created: 2024-06-15 11:44

Cloud SQL

Google's most basic SQL service. While MySQL and PostgreSQL are generally license-free, MS SQL incurs significant additional licensing costs.

Cloud SQL's pricing structure offers four main combinations.

Whether to configure HA or not, and Enterprise vs. Enterprise Plus

Enabling HA allows for automatic failover in case of issues,

and selecting Enterprise Plus provides access to various additional features.

Looking at the prices,

(Each price is listed in the order of basic monthly price / 1-year commitment / 3-year commitment)

vCPU

  • Basic: $39.201 / $29.40075 / $18.81648
  • Basic + HA: $78.402 / $58.8015 / $37.63296
  • Plus: $50.954 / $38.2155 / $24.45792
  • Plus + HA: $101.908 / $76.431 / $48.91584

Memory

  • Basic: $6.643 / $4.98225 / $3.18864
  • Basic + HA: $13.286 / $9.9645 / $6.37728
  • Plus: $8.614 / $6.4605 / $4.13472
  • Plus + HA: $17.301 / $12.97575 / $8.30448

Storage ( SSD )

  • $0.221 / GB, per month
  • $0.442 / GB, per month

Storage ( HDD )

  • $0.117 / GB, per month
  • $0.234 / GB, per month

Maximum Size

  • Enterprise: 96 vCPUs / 624 GB Memory
  • Enterprise Plus: 128 vCPUs / 864 GB Memory

AlloyDB

A database developed using Google's touted storage technology.

Currently, the pricing in the Seoul region (asia-northeast3) is as follows.

  • vCPU: $61.7434 / $46.3112 / $29.638
  • Memory: $10.4682 / $7.8548 / $5.0224
  • $0.38398 / GB, per month
  • Maximum Size: 128 vCPUs / 864 GB Memory



Overall, while HDDs are offered, they are not practically suitable for actual service use except for data backups.

(Their performance is quite low, and there are clear limitations in reading and writing data. And why HDD HA...?)


Although HA configurations are possible for AlloyDB, its inherent SLA is already very good.

Based on your specific needs, refer to the table above and calculate the cost (although it's well documented on the Google home page, it's a bit scattered).


Simply increasing the specifications to match the performance can lead to high-performance service at a good price. However, the process of modifying settings can be a bit tedious.

By the way, AlloyDB is said to offer up to 4 times faster performance than the existing Cloud SQL, but I haven't tested it myself. My current service level hasn't reached that point yet. (Please let your service grow to that level...)


Compared to AlloyDB, Cloud SQL has relatively more limitations, so if your service grows in scale, AlloyDB can be much more cost-effective than Cloud SQL.


Actually, when AlloyDB was first released, I wondered, 'They're releasing this at this price?' Before that, Cloud Spanner was the top-tier Enterprise product. Now, you can understand that AlloyDB sits above Cloud SQL, and Cloud Spanner is above that.

Comments0