Data & storage / 11 / 11
File uploads
A video app where phones upload 180 MB files and thousands watch them. Why bytes should not pass through your API, and how presigned URLs, multipart upload, a worker and a CDN share the job.
- 13 min
- Intermediate
- 11 steps
- Upload p95
- 94 s
- Failed uploads
- 7 %
- Monthly cost
- 1 900 $
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Phone app → APIRequest
POST /videos HTTP/1.1
Host: api.example.com
Authorization1: hidden
Content-Type: multipart/form-data; boundary=x9
Content-Length2: 188743680
<180 MB of video bytes>
Response
HTTP/1.1 201 Created
X-Response-Time3: 94 s
Authorization· hidden — The user's token. A secret, hidden here.Content-Length— 180 MB in one request body. A drop at 99% means starting again.X-Response-Time— 94 seconds for one request. Load balancers and proxies often cut at 60.
Course: 42 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes