4 ms·
# Why I think it was bad Saying "we're the better cloud" is a frail argument. Both GCP and AWS has strengths and weaknesses. People know that. Saying "we're th
by sandstrom 11y ago
# Why I think it was bad
Saying "we're the better cloud" is a frail argument. Both GCP and AWS has strengths and weaknesses. People know that. Saying "we're the best" feels simplistic (and insincere).
Second, some of the things you mention (live migration, scalability, etc) are things that AWS also provide.
# What is good
The last part of your post, So, how can you optimize, was good. It wasn't bashing AWS, it was general, sound advice on how to build things for a cloud platform. More of that would have resulted in a better post.
Nearline is another good offering. You got great publicity on that when it was released recently. I think many felt it had better and simpler pricing, and a better structure for retrieval than glacier. That's what you should focus on.
No need to criticize your competitors or arguing that you're better than them in every dimension. Instead, build good products and let the customer decide.
- milesward 11y agodisclaimer: I'm the OP and work for GCP Sandstrom, thanks for the detailed feedback. Spending most of my day talking with customers, I've found that many, many folks don't really know those strengths and weaknesses very well. This post was written really in direct response to questions we get every day about "why should I choose GCP?" A great example; in your comment you describe AWS as having live migration, which they do not. It's exactly this kind of misinformation that we were aiming to clear up. I hear you loud and clear on more technical guidance; my team has been building http://cloud.google.com/solutions http://cloud.google.com/solutions for the last year, let me know if that helps or if you have any ideas on what we should build next! Thanks again!
- sandstrom 11y agoYes, you are right regarding live migration. I though that's what they used to avoid reboots for one of the Xen-vulnerabilities earlier this year. But it wasn't, it was a hot-patch of some sort. Thanks for clarifying.