Handling Large Blobs hard
How does the 'Resumable Upload' pattern (like TUS protocol) handle network interruptions?
- A It keeps the TCP connection open.
- B It restarts the upload automatically.
- C It uses UDP.
- D The client queries the server for the current offset (HEAD request -> `Upload-Offset: 1000`). It then resumes sending bytes starting from offset 1000 using `PATCH`.
Answer: D. The client queries the server for the current offset (HEAD request -> `Upload-Offset: 1000`). It then resumes sending bytes starting from offset 1000 using `PATCH`.
Stateful tracking of the byte stream allow seamless recovery after hours of downtime.
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)?