4 ms·
It's interesting to see what parts of the product GitLab is struggling with compared to GitHub, e.g. https://githubengineering.com/stretching-spokes/ https://gi
by knownothing 9y ago
It's interesting to see what parts of the product GitLab is struggling with compared to GitHub, e.g. https://githubengineering.com/stretching-spokes/ https://githubengineering.com/stretching-spokes/
- YorickPeterse 9y agoMost of our problems thus far have been the result of misuse of our resources one way or another. GitHub on the other hand probably dealt with these issues earlier on (or are able to hide them somehow, perhaps by throwing a lot of physical hardware at the problem), thus they can now focus on dealing with problems caused by reaching the limits of their (old) systems.
- sytse 9y agoI'm very impressed with the level GitHub database testing is at https://githubengineering.com/mysql-testing-automation-at-github/ https://githubengineering.com/mysql-testing-automation-at-gi... We still got a lot of work ahead of us. But Yorick and Greg their work has been outstanding. Regarding Spokes we're not planning something like that at this time. From https://gitlab.com/gitlab-org/gitaly/issues/650 https://gitlab.com/gitlab-org/gitaly/issues/650 "GitHub eventually moved to Spokes https://githubengineering.com/building-resilience-in-spokes/ https://githubengineering.com/building-resilience-in-spokes/ that had multiple fileservers for the same repository. We will probably not need that. We run networked storage in the cloud where the public cloud provider is responsible for the redundancy of the files. To do cross availability zone failover we'll use GitLab Geo."
- knownothing 9y agoThanks for chiming in, sytse and YorickPeterse! Re: misuse, I remember this incident https://news.ycombinator.com/item?id=11245652 https://news.ycombinator.com/item?id=11245652 made me chuckle and cry a little. If you build it, it will be misused.