A multi-region 311 status store must keep serving during network splits, yet operators also want strong consistency everywhere. What does the CAP theorem imply for this design?
Select an answer to reveal the explanation.
Short Explanation
CAP is the classic "pick your pain" rule when networks split. You cannot crank consistency, availability, and partition tolerance all the way up at the same time. Multi-region 311 status forces a conscious tradeoff, not a free lunch.
Full Explanation
The CAP theorem states that a distributed system facing network partitions cannot simultaneously maximize consistency, availability, and partition tolerance. Multi-region civic status stores operate across unreliable WAN links, so partitions are a realistic concern. Designers therefore choose which property to favor when a split occurs rather than claiming all three at full strength. Understanding this tradeoff is foundational when placing NoSQL workloads across regions.