Blob storage, direct uploads, and CDNs
Photos, videos and files belong in object storage with only their metadata in your database, uploaded straight from the client with a signed URL, split into parts so a dropped connection costs one part instead of the whole file, and served through a CDN whose cache rules you design as carefully as the schema.
What you'll be able to do
- Explain why large bytes go in object storage, and state its consistency, durability and immutability properties
- Design a direct upload with presigned URLs and multipart parts, and compute what a failure costs with and without parts
- Keep the metadata row and the object in step with explicit upload states, events and an orphan sweep
- Set CDN caching for public and private content, choosing versioned URLs over invalidation where possible
Before this: back-of-the-envelope, caching-and-stampedes
Log in to read the rest of this lesson
Photos, videos and files belong in object storage with only their metadata in your database, uploaded straight from the client with a signed URL, split into parts so a dropped connection costs one part instead of the whole file, and served through a CDN whose cache rules you design as carefully as the schema. This walkthrough runs about 22 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.
Log in to continueThe first module of every track is free to read on the web: see what's open in System design.