Task library BRESTORE
Project scope 10 tickets / 3 phases
Total focused work estimate 26h + setup
Suggested stack PostgreSQL · S3-compatible storage · TypeScript Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BRESTORE-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice recovery consistency, integrity validation, and honest recovery objectives.
What the team gains Replace backup-job optimism with a repeatable restoration assessment.
Before you start Create disposable local database and object-store fixtures with synthetic reports; author backup and corruption examples. Delivery agreement Deliver a local restore harness and recovery report; change no production backup policy.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define backup scope and consistency requirements.
PHASE 2 Reconstruct and validate a coherent snapshot.
PHASE 3 Measure recovery and document unrecoverable gaps.
Inventory recovery dependencies Define backup scope and consistency requirements.
BRESTORE-101 Entry ticket; project setup still required Estimated field mix
Site reliability 50% Storage systems 30% Database engineering 20% BRESTORE-102 Depends on BRESTORE-101 Estimated field mix
Storage systems 50% Database engineering 30% Site reliability 20% Restore isolated data Reconstruct and validate a coherent snapshot.
BRESTORE-103 Depends on BRESTORE-102 Estimated field mix
Developer tooling 50% Site reliability 30% Security 20% BRESTORE-104 Depends on BRESTORE-102, BRESTORE-103 Estimated field mix
Storage systems 70% Site reliability 30% BRESTORE-105 Depends on BRESTORE-104 Estimated field mix
Site reliability 40% Database engineering 30% Storage systems 30% BRESTORE-106 Depends on BRESTORE-105 Estimated field mix
Data engineering 60% Site reliability 40% Rehearse disruption Measure recovery and document unrecoverable gaps.
BRESTORE-107 Depends on BRESTORE-105, BRESTORE-106 Estimated field mix
Database engineering 60% Site reliability 40% BRESTORE-108 Depends on BRESTORE-107 Estimated field mix
Site reliability 60% Performance engineering 40% BRESTORE-109 Depends on BRESTORE-104, BRESTORE-108 Estimated field mix
Site reliability 70% Storage systems 30% BRESTORE-110 Depends on BRESTORE-109 Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.