Build a report arrival model that includes top-of-hour bursts
Average reports per minute looks harmless, but nearly every customer chooses 09:00 for its daily report.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Workload modeling · Scheduling
Estimated field mix
- System design50%
- Performance engineering50%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional analytics product lets customers schedule expensive reports at the top of the hour. The API remains available only if report work is admitted and cancelled predictably.
Setup prerequisites
- Create a local scheduler model and synthetic report jobs.
- Use fake execution providers; no customer queries or candidate code run on worker hosts.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Separate average arrival rate from burst size.
- State hypothetical report duration and size classes.
- Include timezone scheduling assumptions.
Implementation constraints
- Create a deterministic synthetic one-day schedule.
Verification to include
- Count average arrivals and the largest one-minute burst.
- Move all schedules to one instant and show the peak changes despite equal daily volume.
Deliverables
- Arrival model and reproducible schedule generator
Rollout and recovery
Review the model before queue sizing; revise assumptions when schedule usage is measured.
Value of the work
For the engineer: Practice workload modeling, fairness and cancellation architecture.
For the team: Review controllable operating costs and predictable customer-facing overload behavior.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.