6 ms·
Looks cool, but the pricing seems a bit non-cloud-native (or at least non-GCP-native). "You are charged each hour for the maximum number of nodes that exist du
by kennethmac2000 10y ago
Looks cool, but the pricing seems a bit non-cloud-native (or at least non-GCP-native).
"You are charged each hour for the maximum number of nodes that exist during that hour."
We've been educated by Google to consider per-minute, per-instance/node billing normal - and presumably all the arguments about why this is the right, pro-customer way to price GCE apply equally to Cloud Spanner.
- advisedwang 10y agoThe per-minute billing is an advantage when you are scaling up and down rapidly. If you use VMs just for 5 minutes, per minute pricing is 20x cheaper than hourly billing. However with a database it is rare to scale up and down rapidly. Rather you expect change over the order of days. Imagine you go from 10 instance to 15 instances over a week. per minute billing only saves a possible 5 instance-hours over the week compared to hourly billing, which is less than 1% saving.