Now the LVCS was created on your local system, which means that teams can’t collaborate with each other using LVCS. Moreover, space can be also a problem in LVCS. So these problems lead to another solution, the emergence of Centralized Version Control System(CVCS). Popular CVCS were being, CVS, Subversion and Perforce. In Centralized Version Control System, many users can simultaneously update the changes at a Central Server as shown below. All data is kept at a single central server, which has its own pros and downfalls.
The benefits include:
- Simultaneously many users can post into single Storage Location.
- Have the ability to control, who can post or who can view only, i.e. has management rights.
The disadvantages include:
- If the Central Server fails to service, the whole user community has to wait until it comes back to their original state.
- If the hard disk of central System damage than the whole data will be lost, if there were no backup.
To overcome the problems of CVCS Distributed Version Control System comes into action. In DVCS, the data is copied not only to a Central Server Database but also between clients Local Database, i.e. When a client collaborates to working repository he not only get the differences between the snapshots but the whole data is copied to his/her Local DataBase of Version Control Tool. It might be said that the DVCS is the Combination of CVCS and LVCS. The popular DVCS are Git, Mercurial etc. The risk of losing data has been minimized.
That’s for all today, a new post will be out soon, that will be totally based on the Git basics, Hope You understand everything very well if you face any issue feel free to comment your issue at Git Forum – https://tekraze.com/forums/forum/git-github/ .Don’t forget to share with your friends, because sharing is caring.