Source Control – Distributed Systems vs. Non Distributed – What’s the difference?

by

The difference is in the publication process:

  • a CVCS (Centralized) means: to see the work of your colleague, you must wait for them to publish (commit) to the central repository. Then you can update your workspace.
    • You are an active producer: if you don’t publish anything, nobody sees anything.
    • You are a passive consumer: you discover new updates when you refresh your workspace, and have to deal with those changes whether you want it or not.

.

  • a DVCS means: there is no “one central repository”, but every workspace is a repository, and to see the work of your colleague, you can refer to his/her repo and simply pulled its history into your local repo.
    • You are a passive producer: anyone can “plug in” into your repo and pull local commits that you did into their own local repo.
    • You are an active consumer: any update you are pulling from other repo is not immediately integrated into your active branch unless you explicitly make it so (through merge or rebase).

Version Control System is about mastering the complexity of the changes in data (because of parallel tasks and/or parallel works on one task), and the way you collaborate with others (other tasks and/or other people) is quite different between a CVCS and a DVCS.

TFS (Team Foundation Server) is a project management system which includes a CVCS: Team Foundation Version Control (TFVC), centered around the notion of “work item”.
Its centralized aspect enforces a consistency (of other elements than just sources)
See also this VSS to TFS document, which illustrates how it is adapted to a team having access to one referential.
One referential means it is easier to maintain (no synchronization or data refresh to perform), hence the greater number of elements (tasks lists, project plans, issues, and requirements) managed in it.

More Related Contents:

  1. Distributed Version Control Systems and the Enterprise – a Good mix? [closed]
  2. Named Branches vs Multiple Repositories
  3. Mercurial — revert back to old version and continue from there
  4. Mercurial: Merging one file between branches in one repo
  5. Git and Mercurial – Compare and Contrast
  6. What is the Difference Between Mercurial and Git?
  7. Git interoperability with a Mercurial Repository
  8. What’s the best three-way merge tool? [closed]
  9. Mercurial for Beginners: The Definitive Practical Guide
  10. Mercurial Subrepos – How do you create them and how do they work?
  11. How to edit incorrect commit message in Mercurial? [duplicate]
  12. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  13. Mercurial: How to ignore changes to a tracked file
  14. Comparison between Centralized and Distributed Version Control Systems [closed]
  15. What is the difference between hg forget and hg remove?
  16. What makes merging in DVCS easy?
  17. What is the cleverest use of source repository that you have ever seen?
  18. git push to multiple repositories simultaneously [duplicate]
  19. IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?
  20. Why is branching and merging easier in Mercurial than in Subversion?
  21. Storing third-party libraries in source control
  22. Is version control (ie. Subversion) applicable in document tracking? [closed]
  23. Locking binary files using git version control system
  24. Re-establish TFS source control bindings
  25. How do I perform a recursive checkout using ClearCase?
  26. Hg: How to do a rebase like git’s rebase
  27. Branching Strategies [closed]
  28. How does git track source code moved between files?
  29. Visual Studio isn’t tracking changes, or checking out files from source control as I edit them
  30. Handling renames: svn vs. git vs. mercurial

Leave a Comment