Version control systems ("VCS", also referred to as source control management or revision control) are a type of software applications that are integral to the success of your software development project. Version control systems provide a standardized way to store your software application's source code, facilitate collaboration between teammates, and most importantly, maintain a historical record of all of the changes that have been made to your source code over time.
Benefits of using version control:
- Protect your software application by storing your source code in a secure way.
- Facilitate collaboration between software developers.
- Provide visibility, traceability, and audibility.
Types of VCS systems
Different software development teams have their own preferences for their VCS workflows. Depending on their project, they might choose one type of VCS tool instead of another.
Distributed VCS systems ("DVCS"), like Git, are the fastest-growing and predominant VCS of choice in the United States. DVCS allows you to “clone” a full copy of the source code repository to your local machine before making changes. Changes are often made to many files under a particular "branch" made within the local copy before creating a "pull request" to "merge" changes back into to the original repository.
Centralized VCS, like SVN or Perforce Helix Core, are the most widely-used version control systems around the globe and are often better suited for projects that involve large repositories, legacy applications, or binary files like design files, art assets (often used in game development), or other documents that cannot be handled in DCVS tools. Centralized VCS tools treat the "central repository" as the source of truth, and typical workflows usually involve three steps:
- "Check out" the latest version of code from the central repository to your local machine. (Often, teams will use "file-locking" features to lock files in the central repository so that you can warn other teammates that you are currently making changes to that file and prevent them from attempting to make simultaneous edits to the same file.)
- Make changes to the file(s) you checked out on your local machine.
- Commit your work to the central repository, with a commit message describing your updates.
Checklist: How to Choose the right VCS for your team
Each version control type provides unique advantages, depending on your team’s previous experience, certain characteristics of your software, and history of your project.
We put together a practical guide to help you determine the right version control for your project, focusing on the three most popular version control types—Git, SVN, and Perforce—and the four key criteria you need to consider when evaluating different repository types.
Read the full analysis below: