That just splits up the task of application server & git executor into two, it doesn't get rid of the dependency on a monolithic storage backend. I understand

That just splits up the task of application server & git executor into two, it doesn't get rid of the dependency on a monolithic storage backend. I understand that this is something gitlab.com is working towards and excited about, presumably because it'll allow for provisioning web workers unrelated to the CPU you're spending on running git, but for us I don't see it being useful. I hope GitLab eventually gets something like GitHub Spokes[1] which'll allow for provisioning the entire setup on a bunch of dumb boxes with RAID 0. 1. https://githubengineering.com/introducing-dgit/ https://githubengineering.com/introducing-dgit/