Multiple ChoiceIntermediate 45s
Read-heavy vs write-heavy design
A classic social feed is 100:1 read:write. Which design choice most directly serves this ratio?
Options
- 1Send all reads to the write leader to keep it simple and avoid any replica lag or ordering issues
- 2Store everything in memory with no persistence at all so that reads never touch a disk device
- 3Use 2PC for every read so that reads always see a consistent snapshot across all of the shards
- 4Shard reads across many read replicas / cache aggressively while writes go to a single leader
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.