Handling Large Blobs hard
To securely resume an upload, how do you verify the integrity of the chunks already on the server?
- A Download them effectively.
- B Check the file size.
- C The server maintains a Merkle Tree or list of checksums for each received chunk. The client verifies which chunks match before sending missing ones.
- D Ask the user.
Answer: C. The server maintains a Merkle Tree or list of checksums for each received chunk. The client verifies which chunks match before sending missing ones.
Size is insufficient (corruption). Hash verification allows 'rolling hash' checks.
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)?