Handling Large Blobs medium
When serving private content (e.g., Premium Video Course) via CloudFront, why use Signed Cookies instead of Signed URLs?
- A Signed URLs work for single files. If usage involves HLS streaming (hundreds of .ts chunks), generatng a URL for each chunk is tedious. A Cookie authorizes the whole folder.
- B Cookies are more secure.
- C Cookies work on mobile only.
- D Signed URLs are expensive.
Answer: A. Signed URLs work for single files. If usage involves HLS streaming (hundreds of .ts chunks), generatng a URL for each chunk is tedious. A Cookie authorizes the whole folder.
Authorization at the 'Session' level vs 'File' level.
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)?