Reject oversized document batches before accepting work
A client submits 50,000 document references in one call. Validation exhausts API memory before the queue sees a single job.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Input limits · Resource bounds · Contract testing
Estimated field mix
- Platform engineering50%
- Performance engineering30%
- API design20%
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 internal document portal creates previews through a trusted mock renderer. Large batches crowd out small teams, failed documents retry forever, and operators lack a safe replay command. This exercise never executes uploaded code or real document macros.
Setup prerequisites
- Queue semantics
- Database transactions
- Operational metrics
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Enforce a documented request byte limit and a maximum of 100 document references.
- Reject duplicate references within the batch with a clear validation reason.
- Create no jobs when batch validation fails.
Implementation constraints
- Validate metadata only; the API must not download or render document contents.
Verification to include
- Accept a valid 100-reference synthetic batch.
- Reject 101 references, excessive bytes, and duplicate references without partial jobs.
Deliverables
- Bounded batch contract and boundary cases
Rollout and recovery
Publish limits before enforcing them on the test client; rollback client batching rather than raising limits without measurement.
Value of the work
For the engineer: Practice asynchronous lifecycle control, fair scheduling, bounded retries, and artifact recovery with a deterministic provider.
For the team: See how an engineer accounts for accepted work and reduces operational toil without granting operators broad data access.
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.