Local Version Control: You have various files, but these files will only display as one file in your computer. This file will record the address of the other version files you have. (You have various files, but these files will only display as one file in your computer. This file will record the address of the other version files you wrote before.)
Centralized Version Control: For collaborative development, Student A and Student B will both go to a central server, most notably SVN, to get their code. If the central server goes down, then all of the history of the files will no longer exist. If the central server goes down, then all the history files will no longer exist. Computer A and Computer B can pull code from the central VCS Server, the representative product is SVN. But the fault is if the Central VCS Server died, no one can pull code from it.)
Distributed Version Control (Distributed Version Control): Everyone has their own local repository, the local repository will exist all the history of the version, even if the central repository hangs, the local also have all the history of the version. (Everyone has their own local repository, everyone should commit to their local repository first and then push it to the Central VCS Server. all history versions.)
