Task library ROLL Platform engineering · Phased project Make a small service release recoverable A fictional scheduling service has an API, a worker, and PostgreSQL. Releases use immutable images on two application instances. The team needs compatibility checks, staged traffic, and a rehearsed rollback without introducing a new orchestration platform.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 30h 30m + setup
Suggested stack TypeScript · OCI image metadata · PostgreSQL · CI workflows 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 ROLL-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice release contracts, compatibility windows, measurable canaries, and incident decisions on a modest application topology.
What the team gains Review whether an engineer can make deployments diagnosable and reversible while identifying when rollback is unsafe.
Before you start HTTP health checks CI pipelines Database migrations Delivery agreement Ten phased issues using a synthetic service and simulated release provider; submit manifests, failure drills, and an operator handoff.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Establish artifact identity and useful health signals.
PHASE 2 Enforce compatibility, serialization, and staged rollout decisions.
PHASE 3 Drain work, diagnose failures, and rehearse rollback.
Know what is running Establish artifact identity and useful health signals.
ROLL-101 Entry ticket; project setup still required Estimated field mix
Platform engineering 70% Site reliability 30% ROLL-102 Entry ticket; project setup still required Estimated field mix
Site reliability 60% Platform engineering 40% ROLL-103 Depends on ROLL-101 Estimated field mix
Platform engineering 80% Security 20% Control release risk Enforce compatibility, serialization, and staged rollout decisions.
ROLL-104 Depends on ROLL-103 Estimated field mix
Database engineering 60% Platform engineering 40% ROLL-105 Depends on ROLL-101, ROLL-103 Estimated field mix
Platform engineering 50% Distributed systems 50% ROLL-106 Depends on ROLL-102, ROLL-104, ROLL-105 Estimated field mix
Site reliability 40% Platform engineering 40% Performance engineering 20% Recover with evidence Drain work, diagnose failures, and rehearse rollback.
ROLL-107 Depends on ROLL-102 Estimated field mix
Platform engineering 50% Networking 30% Site reliability 20% ROLL-108 Depends on ROLL-104, ROLL-105 Estimated field mix
Platform engineering 60% Distributed systems 40% ROLL-109 Depends on ROLL-101, ROLL-106 Estimated field mix
Site reliability 60% Platform engineering 40% ROLL-110 Depends on ROLL-106, ROLL-107, ROLL-108, ROLL-109 Estimated field mix
Platform engineering 50% Site reliability 50% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.