Why we are not leaving the cloud
about.gitlab.com
Why we are not leaving the cloud
1–10 of 216 posts
Re: Why we are not leaving the cloud
#2I'm really glad you guys decided to listen to the experienced commenters' advice and change your mind, rather than obstinately plowing on with what seems to be a bad decision.
Re: Why we are not leaving the cloud
#3It's interesting that the first half of the explanation is largely quotes from a prior HN post's responses.
Does anyone else feel a bit weird seeing off hand comments getting quoted in the explanation for a business decision? I guess we should all get more accustomed to our public input carrying weight in the zeitgeist.
Gitlab's "develop in the open" nature really shows through here. I am not saying that's bad, it's just so different than most startups and established businesses.
Re: Why we are not leaving the cloud
#4A bit disappointed in the article, as the bulk of it is simply quoting various viewpoints, some of which disagree with each other. I'd be much more interested in the thought process that occurred for them to reach the conclusion they did. What internal doubts did they raise? What possible solutions to those doubts did they consider? Things like that.
Re: Why we are not leaving the cloud
#5Buried towards the bottom is the interesting decision to dump CephFS and go with NFS instead.
Re: Why we are not leaving the cloud
#6Buried towards the bottom is the interesting decision to dump CephFS and go with NFS instead.
Fundamentally not much different, though. N shards holding the data, you have to know which shard is which and maintain connections to it. Split brains could happen if that sharding is dynamic etc.
Re: Why we are not leaving the cloud
#7Where is the original thought? There were few hard numbers. There was way too much quoted material and no Gitlab thoughts on it. It looks like they made the post based on feelings instead of a metric like time or dollars.
Re: Why we are not leaving the cloud
#8Hmm. Nearly all the commenters seem to be "extreme", i.e. either full-cloud or full-bare-metal.
Why not go hybrid? Do your baseline load with bare-metal and your spike load with AWS, GCE or Azure Cloud.
Re: Why we are not leaving the cloud
#9Couldn't they have easily just drawn the opposite conclusion? I don't see a strong connection between the article's contents and its conclusion.
Re: Why we are not leaving the cloud
#10Nitpick for the author, you put twaleson for my quote, should be jtwaleson.