3 ms·
At my old company we moved from AWS to GCP mid-2017 - and I honestly can't remember a single major bad thing about it, just two minor ones[0][1]. It was cheape
by wink 9y ago
At my old company we moved from AWS to GCP mid-2017 - and I honestly can't remember a single major bad thing about it, just two minor ones[0][1].
It was cheaper, the VMs performed better, the GUI was better (we heavily used Terraform, but as we just started on GCP, we still used the cloud console quite heavily, to doublecheck, etc)
But! there's surely a bit of bias involved, as we did this as greenfield migration project where we did everything the correct[tm] way with instance groups for scaling etc, whereas the old AWS setup was organically grown. Neither setups had auto-scaling, but on GCP it was really low-friction to scale manually.
[0]: pro: live migrations work / contra: there's NTP clock skew when migrating, this alerted us a few times when we noticed
[1]: terraform and some other tooling didn't yet support 100% of stuff, so we had to file a few bugs/PRs (iirc)