Choose hot and cold archive boundaries with a reviewable decision record
The team proposes a new search cluster before checking whether bounded PostgreSQL search and object retrieval satisfy the workload.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Architecture decisions · Tradeoff analysis
Estimated field mix
- System design50%
- Database engineering30%
- Storage systems20%
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 procurement platform keeps append-only action records. Operators want fast recent search and affordable old records without losing provenance or leaking tenant data.
Setup prerequisites
- Create synthetic audit events and local storage/search adapters.
- Use an explicit fictional retention policy, not legal advice.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Compare existing database search with a separate index option.
- Include consistency, operational and restore costs.
- Choose the smallest option meeting the stated requirements.
Implementation constraints
- Do not provision speculative infrastructure for this design exercise.
Verification to include
- Evaluate both options against recent and old queries.
- Identify the threshold or query need that would reopen the decision.
Deliverables
- Archive storage decision record
Rollout and recovery
Review the decision against the workload model before implementing new infrastructure.
Value of the work
For the engineer: Practice storage tradeoffs, provenance and data-lifecycle decisions.
For the team: Review archive cost and retrieval guarantees before committing to infrastructure.
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.