In this article series we will get a clear understanding of Version Control System Git and GitHub.
Note: this article series will follow this hashtag #vscagghub.
What is a Version Control System ?
Version Control System (also known as Source Control) is a tool which we can use to track, manage and make changes to our code.
Developers can store changes that they make to a file at various stages so they and their fellow developers can retrieve that changes later.
Types:
Based on my research there are 3 types of Version Control Systems that are:
- Local Version Control System
- Centralized Version Control System
- Distributed Version Control System
Local Version Control System (LVCS):
In Local Version Control System data (tracked data) is saved in our local machine.
However, because the files are kept on your local system, this method is extremely vulnerable to errors.
This implies that you run the risk of losing the system file or forget the directory/folder of the file you were working and then write it in another directory
Centralized Version Control System (CVCS):
In this kind of version control system, data is kept on a server that serves as a repository and contains all of the code versions. CVCS helps developers collaborate together.
Despite the useful collaboration and communication amongst developers, there is a danger that you will lose your work if a server goes down for a short period of time or becomes corrupted. Unfortunately, the CVCS has a serious issue with this.
Distributed Version Control System (DVCS):
This is the most commonly used type of VCS.
In a DVCS, each developer has a complete backup (clone) of all the server’s data. This means that even when the server is malfunctioning or unavailable, you can continue working on your project and restore your repositories by copying them to the server.
Many developers can collaborate on a project while using a DVCS. Git is a well-known DVCS, and we’ll talk about it in the next article.
