And one of the advantages of having a zillion different products approach is that you can trust AWS to grow with you and improve their products over time. Same can't be said of GCP.
Compute is compute. Both providers offer similar instance classes for the most part. GCP offers sustained-use discounts, in addition to committed use discounts that match up to reserve instances, plus billing by the minute.
Spot instances can be hugely variable, but cheaper than prremptible. Preemptible offers predictable costs with a guarantee that the instance will go away every 24 hours (and come back).
Network IO is way better.
Inter-region networking comes for free.
GCP ssd persistent disk lands between AWS GP2 and IO1 and gives way more predictable performance.
Local disks can be attached to any instance and end up giving similar performance and being way cheaper than I2 and I3 instances.
Wait until the next post comes up about “serverless” and someone mentions that there are servers involved....
There is no guarantee that the instance will come back. And it can be shut down in under 24 hours. Not that that's a problem compared to AWS or Azure.
>Because preemptible VMs have no availability guarantees, you should design your system under the assumption that any or all of your Compute Engine instances might be preempted and become unavailable. There are no guarantees as to when new instances become available.
https://cloud.google.com/kubernetes-engine/docs/how-to/preem...