File conversion service inspired by CloudConvert and Smallpdf: uploads go to object storage, conversion jobs run on workers from a queue, and results are downloaded from the edge.
See why converting inside the request and storing files in the database does not scale.
What was missing: A conversion should not run inside the request, and files should not live in database rows.
Why that's risky: A heavy conversion occupies a worker thread for seconds, and a handful of large files blocks every other request.
What gets added: One server that receives each upload, converts it while the user waits and keeps the result in the database.
Trade-offs: Simple, but cannot grow.
Keep file bytes in object storage and split uploading from checking.
What was missing: File bytes sit in the database and conversion runs in the request.
Why that's risky: Every status check still hits the job database.
What gets added: File bytes move to object storage and a job database keeps each job's owner, format, status and file location, with separate upload and status services.
Trade-offs: Two stores to keep in sync: store the file first, then write the job.
Serve downloads from the edge and status from memory.
What was missing: Every status check and download reached storage.
Why that's risky: A cached status can show 'pending' for a moment after a job finishes.
What gets added: A cache for job status, which is what clients poll most, and a CDN that serves converted files through short-lived signed links.
Trade-offs: Status may lag by a second or two, which is fine because users poll.
Run conversions in the background and protect uploads.
What was missing: Conversions ran in the request and nothing limited uploads.
Why that's risky: Uploaded files are untrusted input: a malformed file can crash or hang a converter, so each job runs isolated with a time limit.
What gets added: A conversion queue with workers that read the original, convert it and save the result, an upload rate limiter and monitoring.
Trade-offs: Results arrive after conversion finishes, not instantly; the user polls or gets a notification.
You're in the middle of an interview session. Leaving now will end your current attempt.
Explore concept overviews, real-system examples, key tradeoffs, and interview talking points for each roadmap section.
You've conquered this phase. These are the skills you now own: