Distributed vs centralized version control in Git - Hands-On Comparison

Understanding Distributed vs Centralized Version Control with Git

📖 Scenario: You are working on a small team project. You want to understand how version control systems work, especially the difference between centralized and distributed systems. You will practice basic Git commands to see how distributed version control works in real life.

🎯 Goal: Learn how to create a local Git repository (distributed version control), connect it to a remote repository (centralized server), and understand the difference by practicing basic Git commands.

📋 What You'll Learn

Create a local Git repository

Add a file and commit changes locally

Add a remote repository URL

Push local commits to the remote repository

Understand the difference between local and remote repositories

💡 Why This Matters

🌍 Real World

Version control is essential for software development teams to track changes, collaborate, and avoid conflicts.

💼 Career

Understanding Git and the difference between distributed and centralized version control is a key skill for developers, DevOps engineers, and IT professionals.

1

Create a local Git repository

Run the command git init in your project folder to create a local Git repository.

Git

# Run the command to initialize a Git repository
# Your code here

Hint

Use git init to start version control locally.

2

Add a file and commit changes locally

Create a file named README.md with some text, then run git add README.md and git commit -m "Initial commit" to save changes locally.

Git

git init
# Create README.md file and add it to Git
# Your code here

Hint

Create the file with echo or a text editor, then add and commit it.

3

Add a remote repository URL

Run git remote add origin https://example.com/user/repo.git to link your local repository to a remote centralized repository.

Git

git init
echo "# Project Title" > README.md
git add README.md
git commit -m "Initial commit"
# Add remote repository URL
# Your code here

Hint

Use git remote add origin followed by the remote URL.

4

Push local commits to the remote repository

Run git push -u origin main to send your local commits to the remote repository and set the upstream branch.

Git

git init
echo "# Project Title" > README.md
git add README.md
git commit -m "Initial commit"
git remote add origin https://example.com/user/repo.git
# Push commits to remote
# Your code here

Hint

Use git push -u origin main to upload commits and track the remote branch.

Practice

1. Which statement best describes distributed version control systems like Git?

easy

A. Changes are only saved on the server, not locally.

B. Each user has a full copy of the repository including history.

C. Users cannot work offline and must always connect to the server.

D. There is only one central server where all files are stored.

Solution

1. Step 1: Understand distributed version control

   Distributed systems like Git give every user a complete copy of the repository, including all history.

2. Step 2: Compare with centralized systems

   Centralized systems rely on one main server, unlike distributed ones where users work independently.

3. Final Answer:

   Each user has a full copy of the repository including history. -> Option B

4. Quick Check:

   Distributed = full local copy [OK]

Hint: Distributed means full local copy for each user [OK]

Common Mistakes:

• Confusing distributed with centralized control
• Thinking users must always connect to server
• Believing changes are only saved on server

2. Which of the following commands initializes a new Git repository locally?

easy

A. git clone https://example.com/repo.git

B. git commit -m 'start'

C. git push origin main

D. git init

Solution

1. Step 1: Identify command to create new repo

   The command git init creates a new local Git repository.

2. Step 2: Understand other commands

   git clone copies an existing repo; git commit saves changes; git push sends changes to remote.

3. Final Answer:

   git init -> Option D

4. Quick Check:

   Initialize repo = git init [OK]

Hint: Use git init to start a new local repo [OK]

Common Mistakes:

• Using git clone to create a new empty repo
• Confusing commit with init
• Trying to push before creating repo

3. Given a centralized version control system, what happens if the central server goes offline?

medium

A. Users cannot commit or update until the server is back online.

B. Users can continue working and commit locally without issues.

C. Users automatically get a full copy of the repo to work offline.

D. Users can push changes to a backup server automatically.

Solution

1. Step 1: Understand centralized system dependency

   Centralized systems depend on the main server for commits and updates.

2. Step 2: Effect of server downtime

   If the server is offline, users cannot commit or update until it returns.

3. Final Answer:

   Users cannot commit or update until the server is back online. -> Option A

4. Quick Check:

   Centralized needs server online [OK]

Hint: Centralized needs server online to commit [OK]

Common Mistakes:

• Assuming offline commits are possible in centralized systems
• Thinking users get full repo copies automatically
• Believing backup servers sync automatically

4. You cloned a Git repository but forgot to fetch the latest changes. Which command fixes this?

medium

A. git fetch origin

B. git clone --update

C. git push origin main

D. git init

Solution

1. Step 1: Identify command to update local repo

   git fetch origin downloads latest changes from remote without merging.

2. Step 2: Understand other commands

   git clone --update is invalid; git push sends changes; git init creates new repo.

3. Final Answer:

   git fetch origin -> Option A

4. Quick Check:

   Update local repo = git fetch [OK]

Hint: Use git fetch to get latest remote changes [OK]

Common Mistakes:

• Using git clone again instead of fetch
• Trying to push before fetching
• Running git init on existing repo

5. In a distributed version control system like Git, how can multiple users work on the same project without a central server?

hard

A. They cannot work without a central server in distributed systems.

B. They use a single shared folder on a network drive.

C. They share patches and merge changes manually between local repos.

D. They must push all changes to a cloud server immediately.

Solution

1. Step 1: Understand distributed collaboration

   In distributed systems, users have full repos and can share changes as patches or pull requests.

2. Step 2: How users share changes without central server

   They exchange patches or pull changes directly between local repositories manually or via other means.

3. Final Answer:

   They share patches and merge changes manually between local repos. -> Option C

4. Quick Check:

   Distributed = manual patch sharing possible [OK]

Hint: Distributed allows manual patch sharing without central server [OK]

Common Mistakes:

• Thinking distributed needs central server always
• Assuming network shared folder is standard practice
• Believing immediate cloud push is required