Handling Large Blobs hard
Why use Erasure Coding (Reed-Solomon) instead of 3x Replication for cold storage?
- A It reduces storage overhead. 3x Replication requires 200% overhead. Erasure Coding (e.g., 10 data + 4 parity chunks) achieves similar durability with only ~40% overhead.
- B It is more compatible.
- C It is faster.
- D It encrypts data.
Answer: A. It reduces storage overhead. 3x Replication requires 200% overhead. Erasure Coding (e.g., 10 data + 4 parity chunks) achieves similar durability with only ~40% overhead.
The trade-off is higher CPU cost for read/write and higher latency to reconstruct missing data.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Why do modern sites serve images in WebP or AVIF format?
- What does the acronym BLOB stand for?
- Why do we sometimes convert binary images to Base64 strings?
- What is an 'Origin Shield' or 'Mid-Tier Cache' in a CDN architecture?
- For a feed with 100 images, why use 'Lazy Loading'?
- How does HLS/DASH handle a user moving from WiFi to 4G (Variable Bandwidth)?