[thespoonbends]

gitlab.com is down, but are public/private instances are not. Separate failure domains is an advantage of self-hosted.

Github is great, but when it's down, it impacts developers in many places.

When we spread our eggs across many baskets, we are more resilient.

[rvz]

> Separate failure domains is an advantage of self-hosted.

Well the responsibility falls on the infrastructure people in an open-source project as soon as you self-host. But then again many open-source projects already do this. I'd rather have control over my repositories than host them on someone else's server which is why I'd go for self-hosted Gitlab or Gitea.

This has been my point which I have made for self-hosting over the last few months since GitHub was down on a regular basis, and going against locking in their ecosystem, which is another risk. GitLab cloud is no different. [0]

[0] https://news.ycombinator.com/item?id=23915707

[kissgyorgy]

People tend to forget about scale. GitLab need to work for millions of developers and repositories, your self-hosted instance need to work for only a couple of dozens of developers in case of a smaller company, which doesn't even need a distributed system.

[dx034]

I've been using self hosted Gitlab instances for about two years now, maintenance is really low. I've never seen an outage on any of the systems.

Running applications at scale is hard but running Gitlab in a low traffic environment is incredibly stable and low maintenance.

[AirborneUnicorn]

I can agree with this. I maintain a gitlab instance at my place of work and it’s been very resilient for the last two years I’ve been doing it, even with the most mild of attention paid to it.

[sgt]

Our team uses Gitlab. I think we can do fine without Gitlab for a day. It's not like you need it constantly when developing.

[onion2k]

I think we can do fine without Gitlab for a day.

This sounds to me like you've not really bought in to the peripheral software project tools Gitlab offers like boards, issue tracking, CI/CD for running tests, etc. In which case, Gitlab seems a bit like overkill. Running your own git remote is pretty straightforward.

[sgt]

We use a self-hosted Jenkins for CI/CD, tests. Does Gitlab offer anything substantially better in this regard? I am open to moving away from Jenkins but only if it is better. Jenkins is easy to maintain and relatively simple to configure.

[polskibus]

Depends on the day (it's the day we're supposed to release new version!), size of the team, etc It's a devops platform, not just source control.

Disclaimer: we use self hosted gitlab at work.