Why distributed databases handle scale in DBMS Theory - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How distributed databases improve scalability

Which of the following best explains why distributed databases can handle scale better than single-node databases?

A They spread data and workload across multiple machines, allowing parallel processing and storage.

B They store all data on a single powerful server to avoid network delays.

C They compress data to reduce storage size on one machine.

D They use only in-memory storage to speed up access on one node.

💡 Hint

Think about how sharing work among many computers helps handle more data and users.

Distributed databases split data and tasks across many machines. This allows them to process more data and handle more users at the same time, which improves scalability.

📋 Factual

intermediate

Key feature enabling distributed database scaling

What is the main feature that allows distributed databases to scale horizontally?

A Using faster hard drives on a single server.

B Increasing the size of the database on one machine.

C Adding more powerful CPUs to a single server.

D Adding more machines to the database cluster to share load.

💡 Hint

Horizontal scaling means adding more machines, not making one machine stronger.

Horizontal scaling means adding more machines to share the workload, which distributed databases support well.

🔍 Analysis

advanced

Impact of network latency on distributed databases

Which statement correctly describes how network latency affects distributed databases when scaling?

A Network latency can cause delays because data must travel between nodes, potentially slowing some operations.

B Network latency always improves performance as more nodes are added.

C Network latency has no effect because all data is stored locally on each node.

D Network latency is eliminated by using a single central server.

💡 Hint

Consider that nodes communicate over a network, which can add delay.

In distributed databases, nodes communicate over a network. This communication can introduce delays called network latency, which may slow down some operations.

❓ Comparison

advanced

Comparing vertical and horizontal scaling in databases

Which of the following correctly contrasts vertical scaling and horizontal scaling in the context of databases?

A Vertical scaling adds more machines; horizontal scaling upgrades a single machine's hardware.

B Both vertical and horizontal scaling add more machines to the system.

C Vertical scaling upgrades a single machine's hardware; horizontal scaling adds more machines to share the load.

D Vertical scaling reduces the number of machines; horizontal scaling reduces hardware power.

💡 Hint

Think about the difference between making one machine stronger versus adding more machines.

Vertical scaling means improving one machine's hardware (CPU, RAM). Horizontal scaling means adding more machines to share the workload.

❓ Reasoning

expert

Why distributed databases maintain availability during scaling

How do distributed databases maintain high availability when scaling to many nodes?

A By storing all data on a single node to avoid synchronization issues.

B By replicating data across multiple nodes so if one fails, others can serve requests.

C By shutting down nodes during peak load to reduce errors.

D By limiting the number of users to prevent overload.

💡 Hint

Think about how copies of data help keep the system running even if some parts fail.

Distributed databases replicate data on multiple nodes. This means if one node fails, others still have the data and can continue serving users, ensuring availability.

Practice

1. Why do distributed databases handle scale better than single-server databases?

easy

A. Because they spread data and workload across multiple machines

B. Because they use only one powerful computer

C. Because they store data in a single location

D. Because they limit the number of users accessing data

Solution

1. Step 1: Understand the concept of distributed databases

   Distributed databases store data on many computers instead of just one.

2. Step 2: Recognize how spreading data helps scale

   Spreading data and workload means many machines share the work, so the system can handle more data and users.

3. Final Answer:

   Because they spread data and workload across multiple machines -> Option A

4. Quick Check:

   Distributed databases = spread data/workload = better scale [OK]

Hint: Think: More machines share work, so system handles more [OK]

Common Mistakes:

• Thinking a single powerful computer is enough
• Believing data stored in one place scales well
• Assuming limiting users improves scaling

2. Which of the following is a correct reason why distributed databases improve reliability?

easy

A. They store all data on a single server

B. They replicate data across multiple nodes

C. They delete old data regularly

D. They restrict access to one user at a time

Solution

1. Step 1: Identify how reliability is improved in distributed systems

   Reliability means data is safe and accessible even if one machine fails.

2. Step 2: Understand data replication

   Replicating data means copying it to multiple machines, so if one fails, others still have the data.

3. Final Answer:

   They replicate data across multiple nodes -> Option B

4. Quick Check:

   Replication = data copies = better reliability [OK]

Hint: Replication means copies on many machines, so safer data [OK]

Common Mistakes:

• Thinking storing data on one server improves reliability
• Confusing deleting data with reliability
• Believing restricting users improves reliability

3. Consider a distributed database system with 4 nodes. If each node can handle 1000 queries per second, what is the total query capacity of the system?

medium

A. 250 queries per second

B. 1000 queries per second

C. 4000 queries per second

D. 5000 queries per second

Solution

1. Step 1: Understand capacity per node

   Each node can handle 1000 queries per second.

2. Step 2: Calculate total capacity by adding all nodes

   4 nodes x 1000 queries = 4000 queries per second total capacity.

3. Final Answer:

   4000 queries per second -> Option C

4. Quick Check:

   4 x 1000 = 4000 queries/sec [OK]

Hint: Multiply nodes by capacity per node for total [OK]

Common Mistakes:

• Using capacity of one node as total
• Dividing instead of multiplying
• Adding extra queries beyond node capacity

4. A distributed database is not scaling well. Which of the following is a likely cause?

medium

A. The database uses multiple machines

B. Data is replicated on all nodes

C. There are too many nodes handling queries

D. Data is not evenly distributed across nodes

Solution

1. Step 1: Identify what causes poor scaling

   Poor scaling happens if some nodes have too much data or work, causing bottlenecks.

2. Step 2: Understand uneven data distribution

   If data is not spread evenly, some nodes get overloaded while others are idle, hurting performance.

3. Final Answer:

   Data is not evenly distributed across nodes -> Option D

4. Quick Check:

   Uneven data = overloaded nodes = poor scaling [OK]

Hint: Check if data is balanced across nodes for good scale [OK]

Common Mistakes:

• Thinking more nodes always cause poor scaling
• Believing replication causes poor scaling
• Assuming multiple machines hurt scaling

5. A company wants to handle a sudden increase in users without slowing down their database. Which distributed database feature should they focus on to handle this scale?

hard

A. Adding more nodes to share the workload

B. Reducing data replication to save space

C. Storing all data on a single powerful server

D. Limiting user access during peak times

Solution

1. Step 1: Understand the need to handle more users

   More users mean more queries and data requests, requiring more processing power.

2. Step 2: Identify how distributed databases handle increased load

   Adding more nodes spreads the workload, so the system can handle more users without slowing down.

3. Final Answer:

   Adding more nodes to share the workload -> Option A

4. Quick Check:

   More nodes = shared workload = better scaling [OK]

Hint: Add nodes to share work and handle more users [OK]

Common Mistakes:

• Thinking reducing replication improves scaling
• Believing one powerful server can handle all load
• Assuming limiting users is the best scaling method