News for hackers. Stuff that matters.

A comment on GitLab Database Incident – Live Report. Parent comment

Re:GitLab Database Incident – Live Report by luckystartup on Wednesday February 01, 2017 @11:36AM (#13542159)
Maybe it's because I'm familiar with almost all of the gems, but I don't see anything wrong with their Gemfile. It's a pretty complex project, and they really do have a ton of integrations and features that need those gems.

There's probably a few small libraries that they could have rewritten in a few files (never a few lines), but what's the point? The version is locked, and code can always be forked if they need to make changes (or contribute fixes).

[ Parent | on HN ]
Re:GitLab Database Incident – Live Report by debaserab2 on Wednesday February 01, 2017 @12:38PM (#13542874)
> (never a few lines)

You'd be surprised what you can do by carefully considering what the desired outcome actually needs to be.

Maybe there is justification for all the gems in gitlab's Gemfile, I didn't go through it with a fine tooth comb - but this reaffirms my experience that complex projects outgrow monolith codebases. Having an infrastructure outage take down your entire business is kind of a symptom of that.

[ Parent | on HN ]