You can either keep strict consistency on writes or serve always-on reads worldwide. Walk through how you’d reason and decide.

Question

Accepted Answer

Anchor on product impact: user tolerance for stale reads, regulatory needs, and failure stories. If latency and availability are king, prefer AP regions with conflict resolution and client-visible freshness markers. 
If correctness dominates (e.g., financial ledger), choose CP paths, accept higher latency, and invest in queues, retries, and user feedback for occasional write unavailability.

Master Interviews
Anywhere, Anytime

You can either keep strict consistency on writes or serve always-on reads worldwide. Walk through how you’d reason and decide.

Problem Statement

Explanation

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews Anywhere, Anytime

You can either keep strict consistency on writes or serve always-on reads worldwide. Walk through how you’d reason and decide.

Problem Statement

Explanation

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews
Anywhere, Anytime