Live data from Hacker News

2020 Cloud Report: AWS vs. GCP vs. Azure

cockroachlabs.com

91–100 of 124 posts

Re: 2020 Cloud Report: AWS vs. GCP vs. Azure

#92
post #14

Well done Cockroach labs team. This data is very valuable and much appreciated. A small nitpick if you're reading. Fig 19: Sotrage: Azure Write Throughput the y axis has an incorrect label of "1,00" when it should be "1,000"

Cockroach here: Thank you! We'll get this fixed.

A most minor point (and not to detract from the great effort you to went to produce the report): it uses yellow for AWS (good, their logo is yellow/orange) but red for Azure (bad, Azure is ... azure.)

Re: 2020 Cloud Report: AWS vs. GCP vs. Azure

#93

Earlier quoted context omitted.

If there is a cost associated with producing content and that cost can’t be recouped by the presentation of that content (speaker fees at conferences, advertisements, sponsorships, etc) then the content should be sold for a fair market rate. That’s basically the entire point of GDPR. Stop making people trade personal information for “free” content.

No that's not the point of GDPR, it's about choice and control over data. You're free to not share your email if you don't want to read the report. The rest of us can make our own decision.

GDPR literally prohibits you from requiring personal information in exchange for something that doesn’t require that personal information in order to function. You’re right it’s about choice and control over data and “you can only have this thing if you give us unrelated personal data” is not choice nor control.

Re: 2020 Cloud Report: AWS vs. GCP vs. Azure

#94
post #86

Earlier quoted context omitted.

You wouldn’t typically run your databases in a cloud environment on your own VMs - you would use a managed service.

I would never use a managed database service again.

Managed databases are quite good. RDS is very mature and does a very good job with fail over, backups and is very easy to setup.

I don't want to manage anything that needs to be clustered. Technologies like that often need trained engineers with good knowledge of how the product behaves if we want to manage it ourselves.

Re: 2020 Cloud Report: AWS vs. GCP vs. Azure

#95
post #53
post #44

Earlier quoted context omitted.

Meltdown and Spectre did a real number on the c5 and m5 instance types. Amazon's original fix reduced performance substantially, which lot's of people noticed, but no one knew why till the vulnerabilities were announced. Meanwhile Google built a clever workaround which minimized the pain. It was really a mic-drop moment from Google and I wish someone would dig in deep and tell the whole story. At this point I'm sure…

It is less to do with Google investing in GCP offerings than their investment in general in Operating Systems and their sheer quality of engineers.

Which I am sure will also work at Amazon or have worked at Amazon.

Re: 2020 Cloud Report: AWS vs. GCP vs. Azure

#96
post #86

Earlier quoted context omitted.

You wouldn’t typically run your databases in a cloud environment on your own VMs - you would use a managed service.

I would never use a managed database service again.

Alas it's the only way to get decent efficiency on certain cloud platforms. However, you often can't get the custom plugin and modules. On amazon bare metal ephemeral disk instances are decent high performance alternatives but you can't beat aurora for most pg usecases.

Re: 2020 Cloud Report: AWS vs. GCP vs. Azure

#97

Earlier quoted context omitted.

You wouldn't typically run your database VMs on spot/interruptible instances.

why not? Just kidding, but it's getting more common :)

In distributed databases with appropriate grace under churn... Sorry I wasn't clear in my earlier post

Re: 2020 Cloud Report: AWS vs. GCP vs. Azure

#98
post #75
post #72

Earlier quoted context omitted.

Yes, everyone could and will go down at one point or another. Are you saying that your in-house team can manage infrastructure equally well or better than these big public Cloud vendors? They have thousands of site reliability engineers, don't they? The crux of this is how do you compare in managing site reliability. Perhaps you have a world class team you could do that better than yes my point there is moot. But 99%…

Amazon has done a fantastic job of making people think the choice is between them or managing your own infrastructure. Your concerns make no sense in the context that your parent presented: a managed DC. And, frankly, your parent was being generous. Even if you only look at elastic workloads, the workload has to be a) extremely elastic and b) not fall into some pretty common patterns for cloud to make any kind of sen…

To match the reliability of something like an aws managed service, you usually need two or three managed DC's.
Post reply on HN