Bound the waiting queue before worker slots are exhausted
Requests accumulate indefinitely while waiting for a shared dependency.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Backpressure
Estimated field mix
- Site reliability40%
- Platform engineering40%
- Performance engineering20%
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 ticketing service becomes unresponsive during event releases because optional recommendation calls consume the same resources as reservation checks.
Setup prerequisites
- Build a bounded local service and synthetic open-loop workload generator with controllable dependency delays.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Enforce a finite waiting capacity.
- Return a documented overload response when full.
- Remove cancelled requests from the queue.
Implementation constraints
- Never report rejected requests as successful degradation.
Verification to include
- Admit work below the limit.
- Overflow and cancel queued requests without leaked slots.
Deliverables
- Bounded admission queue.
Rollout and recovery
Start with conservative limits; restore the previous policy if essential outcomes regress.
Value of the work
For the engineer: Practice overload behavior, admission control, and fair performance experiments.
For the team: Create predictable failure and degradation behavior under declared capacity constraints.
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.