How can you combine transaction history with caching to improve read performance without sacrificing data consistency?

hard📝 Trade-off Q9 of Q15

LLD - Design — Splitwise (Expense Sharing)

AUse a cache that updates only after a delay

BUse a write-through cache that updates cache and database simultaneously

CCache only the oldest transactions

DDisable caching to avoid stale data

Step-by-Step Solution

Solution:

Step 1: Understand caching strategies
Write-through cache updates both cache and database immediately, ensuring consistency.
Step 2: Compare with other options
Delayed updates cause stale reads; caching oldest data is inefficient; disabling cache reduces performance.
Final Answer:
Use a write-through cache that updates cache and database simultaneously -> Option B
Quick Check:
Consistent caching = write-through cache [OK]

Quick Trick: Write-through cache keeps data consistent [OK]

Common Mistakes:

MISTAKES

Master "Design — Splitwise (Expense Sharing)" in LLD

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More LLD Quizzes