Business processes / 10 / 12
Bulk import
A wholesale company uploads its product catalog as a CSV: 200 000 rows. Parsing it inside the request times out, eats memory and throws everything away for one bad row. The file goes to object storage instead, an import job streams it, validates every row and reports errors, survives restarts and repeated uploads, writes in short batches, shows progress and stays within per-tenant limits.
- 13 min
- Intermediate
- 12 steps
- Import time
- 3 s
- Rows imported
- 100 %
- API memory
- 180 MB
- Checkout lock wait
- 0 s
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Browser → App APIRequest
POST /products/import HTTP/1.1
Host: app.example.com
Cookie1: hidden
Content-Type2: multipart/form-data; boundary=x9
Content-Length3: 412380
Response
HTTP/1.1 200 OK
{
"imported": 42000,
"took_ms": 3120
}
Cookie· hidden — The user's session. Hidden here.Content-Type—multipart/form-data, the browser's form upload: the file travels through the web server.Content-Length— 412 KB. The web server keeps all of it while the request runs.imported— Every row in one go, all or nothing.
Build it yourselfCheat sheetCompare lessons
Course: 74 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes
11 Case studies