3 ms·
Googler, opinions are my own. I don't work on cloud. While AWS is more popular and has more public documentation and blogs, One thing I've heard about gcp that
by kyrra 2y ago
Googler, opinions are my own. I don't work on cloud.
While AWS is more popular and has more public documentation and blogs, One thing I've heard about gcp that people seem to love a More consistent UI and CLI. Features also tend to interop better.
But when you have those is some of your driving goals, it can slow down the rollout of new features. It's also very possible to use gcp without doing lock-in, if you stay away from specialized services like spanner.
- influx 2y agoA Googler who benefits from GOOG RSU going brrr says Google is better than a competitor. OK? Are you authorized to speak on Google's behalf publicly?
- kyrra 2y agoOur market share in cloud speaks volumes. We had a huge start with AppEngine. But for some reason we failed to launch. I'd guess it was a lack of support and enterprise hand holding. the cloud team hasbeen trying to play catch-up there, and it's just taking a lot of work.
- kyruzic 2y agoHe even started his comment like it had been approved by lawyer first lol
- kyrra 2y agoHa. Nope. I post a bunch of nonsense on the Internet, but if I'm writing about anything Google, I will always start with that message. I am definitely skewed by being paid to work there. Also, I've never ran anything I've written about Google online by anyone internally.
- yas_hmaheshwari 2y ago> More consistent UI and CLI. Features also tend to interop better I agree with this part of the statement. Having used both AWS and GCP, GCP seems a bit easier to navigate > if you stay away from specialized services like spanner Don't agree with this one. Once you are in one cloud, you are locked-in. Using services like BigQuery, Google pub-sub would eventually lock you in
- scarface_74 2y agoFormer AWS ProServe employee - I did work in cloud and had some part in quite a few migrations. I did my bid at BigTech and I have no love loss for Amazon. You can not use any service at scale and avoid “lock in”. “Infrastructure has weight”. I’ve seen it take over a year to migrate an organizations VMWare hosted VMs to AWS. No “just use Kubernetes” is not the answer. Every hosted Kubernetes provider has some type of custom metadata you need to add to your configuration. It can be leaky. No “just use Terraform” is not the answer. Providers are unique for each cloud platform and you still have to rewrite everything. Not to mention at scale, you have to deal with the PMO, compliance, training, if you are large enough you might have a physical connection from your Colo to the provider etc..