Consistency models (strong, eventual) in HLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is strong consistency in distributed systems?

Strong consistency means that after a write completes, all reads will see that write immediately. It's like everyone always sees the latest version of data, no matter which server they ask.

beginner

Define eventual consistency.

Eventual consistency means that if no new updates happen, all copies of data will become the same eventually. But right after a write, some reads might see old data for a while.

beginner

Give a real-life example to explain strong consistency.

Imagine a bank account balance. If you deposit money, strong consistency means every teller and ATM immediately shows the new balance to everyone.

intermediate

Why might a system choose eventual consistency over strong consistency?

Because eventual consistency allows faster responses and better availability by letting some servers be temporarily out of sync. It's useful when perfect up-to-date data is not critical.

intermediate

What is a common tradeoff between strong and eventual consistency?

Strong consistency gives up some speed and availability to ensure all users see the same data immediately. Eventual consistency gives up immediate accuracy to gain speed and availability.

Which consistency model guarantees that all reads see the latest write immediately?

A Weak consistency

B Strong consistency

C Causal consistency

D Eventual consistency

Strong consistency ensures all reads reflect the most recent write immediately.

In which consistency model can reads temporarily return stale data after a write?

A Eventual consistency

B Strong consistency

C Linearizability

D Sequential consistency

Eventual consistency allows temporary stale reads but guarantees data will converge eventually.

Which is a benefit of eventual consistency?

A Simpler programming model

B Immediate data accuracy

C Higher availability and performance

D No data conflicts

Eventual consistency improves availability and performance by allowing temporary data divergence.

Strong consistency is most important for which type of application?

A Social media feeds

B Video streaming

C Caching static content

D Banking transactions

Banking requires accurate, up-to-date data, so strong consistency is critical.

What does eventual consistency guarantee if no new updates occur?

A Data will converge to the same value

B Data will remain inconsistent

C Data will be lost

D Data will be immediately consistent

Eventual consistency guarantees that all replicas will converge to the same data eventually.

Explain the difference between strong consistency and eventual consistency using a simple analogy.

Think about how quickly everyone sees an update in different situations.

Describe scenarios where eventual consistency is preferred over strong consistency and why.

Consider tradeoffs between accuracy and performance.

Practice

1. Which statement best describes strong consistency in distributed systems?

easy

A. All users see the same data immediately after an update.

B. Data updates are delayed and may differ temporarily between users.

C. Data is never synchronized between nodes.

D. Users see different versions of data permanently.

Solution

1. Step 1: Understand strong consistency definition

   Strong consistency means every read returns the most recent write, so all users see the same data instantly.

2. Step 2: Compare options with definition

   All users see the same data immediately after an update. matches this definition exactly, while others describe delayed or inconsistent views.

3. Final Answer:

   All users see the same data immediately after an update. -> Option A

4. Quick Check:

   Strong consistency = immediate data sync [OK]

Hint: Strong consistency means instant data visibility everywhere [OK]

Common Mistakes:

• Confusing strong consistency with eventual consistency
• Thinking data can be permanently inconsistent
• Assuming delays are allowed in strong consistency

2. Which of the following is a correct characteristic of eventual consistency?

easy

A. No synchronization happens between nodes.

B. All nodes update simultaneously with no delay.

C. Data is always consistent after every write operation.

D. Data updates propagate over time and become consistent eventually.

Solution

1. Step 1: Recall eventual consistency meaning

   Eventual consistency means updates may take time to reach all nodes, but eventually all nodes will have the same data.

2. Step 2: Match options to definition

   Data updates propagate over time and become consistent eventually. correctly states that data updates propagate over time and become consistent eventually.

3. Final Answer:

   Data updates propagate over time and become consistent eventually. -> Option D

4. Quick Check:

   Eventual consistency = delayed but eventual sync [OK]

Hint: Eventual consistency means data sync happens over time [OK]

Common Mistakes:

• Assuming immediate synchronization in eventual consistency
• Confusing no synchronization with eventual consistency
• Thinking eventual consistency means permanent inconsistency

3. Consider a distributed database using eventual consistency. If a user updates a record on one node, what is the expected behavior immediately after the update?

medium

A. Other nodes may temporarily show the old record until synchronization completes.

B. All other nodes instantly reflect the updated record.

C. The update is rejected until all nodes confirm availability.

D. The record is deleted from all nodes except the updated one.

Solution

1. Step 1: Analyze eventual consistency update behavior

   In eventual consistency, updates propagate asynchronously, so other nodes may temporarily have stale data.

2. Step 2: Evaluate options against this behavior

   Other nodes may temporarily show the old record until synchronization completes. correctly states that other nodes may show old data until synchronization finishes.

3. Final Answer:

   Other nodes may temporarily show the old record until synchronization completes. -> Option A

4. Quick Check:

   Eventual consistency = temporary stale reads [OK]

Hint: Eventual consistency allows temporary stale data [OK]

Common Mistakes:

• Expecting instant update on all nodes
• Confusing update rejection with consistency model
• Assuming data deletion on other nodes

4. A system claims to provide strong consistency but users report seeing outdated data after updates. What is the most likely cause?

medium

A. The system uses synchronous replication correctly.

B. The system is actually using eventual consistency under the hood.

C. Users are refreshing their data too often.

D. The network is too fast causing data to update too quickly.

Solution

1. Step 1: Understand strong consistency guarantees

   Strong consistency guarantees all users see the latest data immediately after update.

2. Step 2: Analyze why outdated data appears

   If users see outdated data, the system likely does not enforce strong consistency, possibly using eventual consistency instead.

3. Final Answer:

   The system is actually using eventual consistency under the hood. -> Option B

4. Quick Check:

   Outdated data means no strong consistency [OK]

Hint: Outdated data means strong consistency is not enforced [OK]

Common Mistakes:

• Blaming network speed for outdated data
• Assuming user refresh frequency causes inconsistency
• Confusing synchronous replication with eventual consistency

5. You are designing a global e-commerce platform. Which consistency model should you choose for the inventory stock count to ensure customers never buy more items than available, and why?

hard

A. Eventual consistency, because it improves performance and availability.

B. No consistency model is needed for inventory data.

C. Strong consistency, because it guarantees all users see the latest stock count immediately.

D. Use eventual consistency with no synchronization.

Solution

1. Step 1: Identify critical data requirements

   Inventory stock count must be accurate to prevent overselling, requiring immediate data correctness.

2. Step 2: Choose consistency model based on requirements

   Strong consistency ensures all users see the latest stock count instantly, preventing overselling.

3. Final Answer:

   Strong consistency, because it guarantees all users see the latest stock count immediately. -> Option C

4. Quick Check:

   Critical data needs strong consistency [OK]

Hint: Critical data needs strong consistency for accuracy [OK]

Common Mistakes:

• Choosing eventual consistency for critical stock data
• Ignoring consistency needs for inventory
• Assuming no consistency is acceptable