Problem Statement
You must choose between strong and eventual consistency for a user feed. Justify your choice and mitigation.
Explanation
For feeds, eventual consistency is fine if users tolerate brief staleness. You gain low latency and high availability using caches and replicas. Add freshness markers and client pull-to-refresh for critical actions.
If strict correctness is required, confine strong consistency to write paths or small critical reads, then fan-out later. This narrows the expensive guarantees to where they matter.
Code Solution
SolutionRead Only
Header: X-Data-Freshness: ~5s
Practice Sets
This question appears in the following practice sets:
