Handling Large Blobs hard
When tuning chunk size for Multipart Upload (e.g., 5MB vs 100MB), what is the trade-off?
- A Large chunks are faster.
- B It doesn't matter.
- C Small chunks are more secure.
- D Small chunks = Higher overhead (more API calls). Large chunks = Wasted bandwidth on retry (if 99MB of a 100MB chunk succeeds and fails, you re-send 100MB).
Answer: D. Small chunks = Higher overhead (more API calls). Large chunks = Wasted bandwidth on retry (if 99MB of a 100MB chunk succeeds and fails, you re-send 100MB).
Balance overhead against failure penalty. 5-10MB is a common sweet spot for mobile.
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)?