Architecture Simulator

The Render Queue

You work on a design tool. Two of its features are expensive. "Generate a layout for me" runs a model. "Export as MP4" renders video. Both take seconds to minutes, both need accelerated hardware, and both are requested from a web page by someone who is watching a spinner. The finished files are large and are downloaded far more often than they are produced. A job that runs twice costs you twice and, for billing, may charge the customer twice. Traffic is mostly people browsing and editing. Only a small fraction of requests actually start a job -- but that fraction is where the money goes.

Must meet

p99 latency: ≤ 300ms
Availability: ≥ 99.90%
Budget: ≤ $9000/mo
Durability: durable
Consistency: read-your-writes

The system does

·Accounts and login
·Users upload files
·Work happens after the response

Components

Drag onto the canvas, or tap one and then tap where it goes. Not everything here belongs in every design — picking the wrong component is part of the exercise.

TrafficA normal weekday · 200 rps peak

p99 0msavail 0.00%cost/mo at peak $0