Migrations, Volumes, and Stateful-Service Rules
Phase 32 objective: containerize the existing architecture without moving durable state, secrets, or business responsibilities into the container layer.
Migrations Prisma migrate deploy belongs in an explicit migration job/release step. It should not run independently in every horizontally scaled API replica. deployment | +--> migration job (once) | | | v | PostgreSQL schema | +--> API replicas | +--> Web replicas
Volumes Local PostgreSQL data can use a named Docker volume. Production managed PostgreSQL remains outside the application container.
Rule Container replacement should be normal. If replacing an API or web container loses business data, the architecture placed durable state in the wrong location.
Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.
Restate the goal of “Migrations Volumes and Stateful Service Rules” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Dockerfiles and compose/dev verification that build and run TaskFlow services from clean inputs.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const tasks = await prisma.task.findMany({
where: { workspaceId },
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: 20,
});Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.
Read the generated SQL before applying it and compare the change against existing production-shaped data.
Without copying the final source, create a second small scenario that applies “Migrations Volumes and Stateful Service Rules” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Run the container with runtime env vars and map the service port explicitly.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Running development server in production container
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.