News for hackers. Stuff that matters.
Re:How We Knew It Was Time to Leave the Cloud by Maarten88 on Sunday November 13, 2016 @06:34AM (#12942872)
Yes, write a Git backend using a distributed actor system, like Akka, Orleans or Service Fabric, backed by Table Storage, Bigtable or some other distributed hashtable store. Git maps naturally to this structure, using git hashes as table index.

You'll have a really cheap and very scalable solution that uses low level storage mechanisms yet it will also be really performant because when loaded everything will be served from memory.

Re:How We Knew It Was Time to Leave the Cloud by sytse on Sunday November 13, 2016 @07:58AM (#12943113)
For sure, and people are trying to do this on the basis of libgit2. But so far nobody has been able to make it work for all of the cases. Even GitHub is using filesystems as far as I know.
Re:How We Knew It Was Time to Leave the Cloud by markelliot on Sunday November 13, 2016 @12:03PM (#12944263)
One of the teams I work closely with used JGit's extensibility to run git on top of a KVS: https://medium.com/@palantir/stemma-distributed-git-server-7...

Notably this doesn't require a distributed filesystem.

Re:How We Knew It Was Time to Leave the Cloud by sytse on Sunday November 13, 2016 @06:19PM (#12946368)
That looks really interesting, thanks for posting. I added it to our issue https://gitlab.com/gitlab-com/infrastructure/issues/727#note...
Re:How We Knew It Was Time to Leave the Cloud by ethomson on Monday November 14, 2016 @05:00AM (#12948683)
For Visual Studio Online and TFS, Microsoft is using libgit2 and some custom ASP.NET code for the upload-pack / receive-pack endpoints, stuffing the data into SQL Azure. No filesystem, no `git` executable.
Re:How We Knew It Was Time to Leave the Cloud by nixgeek on Sunday November 13, 2016 @08:48PM (#12946952)