Your database didn’t fail.
You picked the wrong trade-off.
The CAP theorem forces every distributed system to make a choice: consistency or availability during network partitions.
This is the part every tutorial skips:
Network partitions aren’t edge cases. They are inevitable. Every system you build will face them.
The real question isn’t “can I have both?” — it’s “which one do I sacrifice?”
HOW THE GIANTS HANDLE IT
<ol>
<li>
NETFLIX (AP - Availability wins)
Your “Continue Watching” list might differ across devices for a few seconds. Netflix doesn’t care.
They use Cassandra with LOCAL_QUORUM writes. If nodes are unreachable, writes still succeed and sync later.
Result: You always get to watch. Sometimes with slightly stale recommendations.
</li>
<li>
DYNAMODB (Tunable)
Amazon’s secret: they let YOU decide per operation.
Eventually consistent reads give single-digit millisecond latency globally.
Strongly consistent reads are available when you absolutely need accuracy.
</li>
<li>
GOOGLE SPANNER (CP - Consistency wins)
Financial transactions? Inventory management?
Spanner accepts the latency hit for global consistency.
It is slower. But your bank balance is never wrong.
</li>
</ol>
BEYOND CAP: PACELC
CAP only covers partition scenarios. PACELC extends it to normal operations.
During a partition: choose Availability or Consistency.
Normal operation: choose Latency or Consistency.
Cassandra is PA/EL: fast and available, eventually consistent.
Spanner is PC/EC: consistent always, accepts the latency cost.
THE REAL ENGINEERING DECISION
What can your users tolerate?
Social media post not appearing for 2 seconds? Acceptable.
Payment double-charging a customer? Catastrophic.
Choose your database based on the failure mode you can survive.
What is the most painful consistency trade-off you’ve had to make in production?
<a href="https://www.linkedin.com/search/results/all/?keywords=%23systemdesign&amp;origin=HASH_TAG_FROM_FEED" target="_blank" rel="noopener nofollow">#SystemDesign</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23distributedsystems&amp;origin=HASH_TAG_FROM_FEED" target="_blank" rel="noopener nofollow">#DistributedSystems</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23backendengineering&amp;origin=HASH_TAG_FROM_FEED" target="_blank" rel="noopener nofollow">#BackendEngineering</a>

CAP Theorem