From Memory to Durable State Why the storage lifetime must move beyond the Node.js process
Phase 11 - Persistent Task CRUD API Volume 03 - Database Engineering
Architecture milestone In-memory Todo API
↓
↓
Phase 11 replaces process memory with durable PostgreSQL-backed application behavior.
Memory solved the wrong problem The array from Phase 05 was useful because it isolated HTTP behavior. It was never meant to be durable storage. A process-local array belongs to one running Node.js process; when that process stops, the array stops existing with it.
Figure 1 - The persistence gap POST /todos
↓
↓
↓
data disappears
The failure is not a bug in HTTP. It is a storage-lifetime problem.
Durable state changes the ownership model Once Task rows live in PostgreSQL, NestJS no longer owns their lifetime. NestJS owns the rules for creating and changing them; PostgreSQL owns durable storage and relational constraints.
Integrity Application discipline Application + database constraints
Why we move from Todo to Task Phase 10 established Task as a real domain entity: it belongs to a Project, has a status and priority, and can later be assigned to a User. We therefore evolve the API to /tasks instead of keeping a fake Todo resource disconnected from the production model.
The same transition happens when a prototype PayrollRun, PurchaseRequest, LeaveRequest, or InventoryMovement stops being a JavaScript object and becomes durable business data.
Persistence does not remove the service layer A common beginner mistake is to treat Prisma as the service. Prisma knows how to access data; it does not know TaskFlow business semantics. The service remains the place where application rules and meaningful not-found behavior live.
Figure 2 - Responsibility boundary TasksController: HTTP input/output
↓
↓
↓
Each layer becomes easier to change because its responsibility is explicit.
What changes and what stays stable • HTTP verbs and REST resource semantics from Phase 05 remain valid.
• CORS and fetch behavior from Phase 06 remain valid.
• The storage implementation changes from memory to PostgreSQL.
• The data model from Phase 10 becomes executable schema.
• The frontend still talks to an HTTP API; it never receives database credentials.
From Memory to Durable State matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “From Memory to Durable State” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: value → owner → lifetime → source of truth → consumer. 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: Working /tasks API supporting create/list/read/update/delete against PostgreSQL with consistent error behavior.. 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.
API task rows -> TanStack Query
Search/filter URL -> URL/search params
Create form fields -> React Hook Form
Dialog open/closed -> local UI state
Authenticated user -> auth/session stateDo 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.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “From Memory to Durable State” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Define Task create/update/read response shapes before implementation.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Controllers contain Prisma calls
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.