Test read-only degradation when enrollment writes are unavailable
A database write outage should not make the entire course catalog disappear.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Graceful degradation
Estimated field mix
- Site reliability60%
- Backend40%
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 course platform expects a registration deadline spike. Capacity assumptions, escalation ownership, and degradation decisions are scattered across old documents.
Setup prerequisites
- Create synthetic registration traces and local dependency doubles with finite connection and request limits.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BREADINESS-101 · Turn the registration forecast into a workload envelope
- BREADINESS-102 · Inventory dependency quotas and exhaustion behavior
- BREADINESS-103 · Add connection-pool wait time to registration diagnostics
- BREADINESS-104 · Exercise registration idempotency during client reconnects
- BREADINESS-105 · Decouple confirmation delivery from accepted registration
Acceptance criteria
- Preserve declared safe read behavior.
- Fail enrollment explicitly when writes cannot commit.
- Show data age when serving a cached catalog.
Implementation constraints
- Never queue unacknowledged enrollments invisibly.
Verification to include
- Read the catalog during a write failure.
- Attempt enrollment and verify no false confirmation.
Deliverables
- Write-outage behavior.
Rollout and recovery
Enable only documented degradation; clear stale cache on incompatible catalog changes.
Value of the work
For the engineer: Practice readiness reviews, capacity reasoning, and cross-functional operational handoffs.
For the team: Produce a concrete launch-readiness assessment with measurable risks and recovery actions.
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.