| 1 | Complexity | When we say about the Centralized Version Control System it is very easy to understand for beginners. | And when we say about the Distributed Version Control System it is not easy for beginners as have some complex process. |
| 2 | Approach | When we say about the Centralized Version Control System it is based on the client-server approach. | When we say about the Distributed Version Control System approach it is also based on client-server approach. |
| 3 | Repository | When we say about the Centralized Version Control System its repository is placed at one place and delivers information to many clients. | But when we say about the Distributed Version Control System here every user has a local copy of the repository in place of the central repository on the server-side. |
| 4 | Concept | When we say about the CVCS it is most straightforward system based on the concept of the central repository. | When we say about the DVCS it is flexible and has emerged with the concept that everyone has their repository. |
| 5 | Latest Code | When we say about the CVCS here server provides the latest code to all the clients across the globe. | When we say about DVCS here every user can check out the snapshot of the code, and they can fully mirror the central repository. |
| 6 | Users and Access | When we say about the CVCS it very easy to administrate and has additional control over users and access by its server from one place. | When we say about the DVCS it is fast when we compare this with CVCS as we donot have to interact with the central server for every command. |
| 7 | Popular Tool | When we say about the Centralized Version Control System there are popular tools like SVN(Subversion) and the CVS. | There are many popluar tools of DVCS like Git and Mercurial. |
| 8 | Access Data | In CVCS if server fails, no other system can access data from another system. | If in DVCS if any of server fails otehr system were collaborating via it, that server can restore any of the client repositories. |