3 ms·
Git Docs... - https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control https://git-scm.com/book/en/v2/Getting-Started-About-Version... "...The next
by belter 4y ago
Git Docs... - https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control https://git-scm.com/book/en/v2/Getting-Started-About-Version...
"...The next major issue that people encounter is that they need to collaborate with developers on other systems. To deal with this problem, Centralized Version Control Systems (CVCSs) were developed. These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients that check out files from that central place. For many years, this has been the standard for version control."
"...However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything..."
"...This is where Distributed Version Control Systems (DVCSs) step in. In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don’t just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history. Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it. Every clone is really a full backup of all the data...."
- williamvds 4y agoGit avoids the problem where the central service being down gets in the way of local development. Even in Git, that central service going down means degraded collaboration. Normally a Git remote is just an ssh-accessible machine, and so pretty resilient. But GitHub is a lot more complex, so apparently that simple service went down, along with all the features they built on top of it
- imglorp 4y agoYou don't actually need the central service. In an emergency, a team could work entirely over email via diffs like Linus does.
- williamvds 4y agoYeah, true. In this case, I'm sure most teams did what mine did, and waited for the outage to be resolved. The development workflow and CI/CD is so tightly coupled to the Git remote, it would have taken a while to create and switch to another remote.
- cesarb 4y agoI once used another alternative: each member of the team runs git-daemon on their desktop to export their local repository, and adds the repositories exported by the other members of the team as git remotes. You can merge a coworker's master branch to your master branch whenever you want to get their changes (and the changes they already merged), which makes for a chaotic but fun development experience.
- vmilner 4y agoI’m not a big Git/GitHub user but presumably distributed version control is still superior to Systems like Subversion that don’t provide a full clone of the repo, as you can still work during GitHub downtime and then use the good branch merging tools to merge back after the outage?