Provide retry guidance that does not synchronize every client
All rejected clients retry exactly one second later and recreate the spike.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Retry design
Estimated field mix
- API design50%
- Site reliability50%
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
- Return bounded retry guidance.
- Document jitter and attempt ceilings for clients.
- Avoid automatic retry of unsafe writes.
Implementation constraints
- Use deterministic random input in tests.
Verification to include
- Spread synthetic client retries across the window.
- Verify non-idempotent requests are not blindly retried.
Deliverables
- Overload response contract.
Rollout and recovery
Publish guidance with admission changes; monitor repeated rejection bursts.
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.