Build the MVP: request walkthrough and lab
Part of the Staff AI System Design course. Everything runs in your browser and makes no network requests. Every figure is illustrative.
Request Lifecycle: Advance One Boundary at a Time
Step 1 of 6: Client
- Responsible component
- Input
- Output and durable state
- Possible failure
This is a contract model, not a live request. Early validation, identity, duplicate, and insert failures are described at their step; the selected scenario varies the model/final-write outcome.
10. Lab: Move the Deadline, Observe the Outcome
Try the provider deadline
Deterministic timing model. No API call, queue, or measured benchmark.
201 completed
Client duration 2620 ms; fixed overhead 120 ms.
The answer commits before success. Provider time remains within its deadline.
The worked cases below remain available without scripting. This model assumes successful state writes and ignores network tails.