Queue puzzle
Move slow work out of the request
Uploading a video triggers transcoding, thumbnails, notifications, and search indexing.
Puzzle target
Pick what should be queued so the request can return quickly and workers can retry safely.
Not selected yet
Not selected yet
Not selected yet
Complete each design choice to unlock the review. The feedback above will point out what your current tradeoff misses.
Flash cards
Review the key moves
What is the main idea behind System Design: Queues and Async Work?
Lesson checks
Practice each idea before moving on
Short Mimo-style checks built from this lesson's code, terms, and sequence.
Which statement best captures the main point of this lesson?
Put the learning moves in the order that makes the concept easiest to apply.
System design is a sequence of explicit tradeoffs. Start small: clarify the goal, estimate load, pick the simplest architecture, then name what breaks first.
| Design surface | What you decide |
|---|---|
| Requirements | Functional behavior, constraints, and non-goals |
| Scale | Reads, writes, storage, bandwidth, and latency target |
| Architecture | Clients, load balancer, services, cache, database, queue, and workers |
| Reliability | Failure mode, fallback, retry, and metric |
| Goal | Move slow or retryable work behind a queue without losing idempotency. |
Practice Task
- Decide what runs synchronously, what enters the queue, and how workers retry safely.
- Use the design puzzle below to choose components and tradeoffs.
- Explain the bottleneck before adding more infrastructure.