Transactions and the Repository Boundary Volume 07 - Advanced Application Architecture | Phase 24
Repositories make transactions harder if designed carelessly A transaction spanning Task, Membership, Project, audit records, and notifications is an application workflow. Hiding every table behind an isolated repository can make it difficult to guarantee that all writes share the same Prisma transaction client.
TaskFlow decision Phase 24 does not introduce a generic UnitOfWork or transaction manager yet. Single-repository atomic operations may use Prisma transactions internally. Cross-feature transactional orchestration remains explicit until repeated pressure justifies a dedicated abstraction.
Good internal transaction const [rows, total] = await prisma.$transaction([ prisma.task.findMany({ where, ...page }), prisma.task.count({ where }), ])
Warning sign service -> TaskRepository -> MembershipRepository -> AuditRepository -> ??? how do all three share one transaction?
Rule Do not weaken atomicity just to preserve a repository pattern. Persistence abstraction is secondary to correctness.
Prisma context Prisma 7 still distinguishes nested writes, sequential/batch transactions, and interactive transactions. Those mechanics remain implementation concerns, but the transaction boundary should be chosen by the application workflow.
ORMs do not remove the database. SQL literacy lets you reason about correctness, constraints, query cost, transactions, and the evidence stored in PostgreSQL.
Restate the goal of “Transactions and the Repository Boundary” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: application intent → SQL statement → query planner → table/index → rows returned. 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: One TaskFlow aggregate/use case refactored behind a purposeful repository interface with real database integration tests.. 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.
SELECT t.id, t.title, u.name AS assignee
FROM tasks AS t
LEFT JOIN users AS u ON u.id = t.assignee_id
WHERE t.workspace_id = $1
ORDER BY t.created_at DESC, t.id DESC;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.
Capture EXPLAIN ANALYZE, row counts, filters, sort keys, and indexes before adding an index.
Inspect join cardinality and constraints; do not hide a modeling bug with DISTINCT until you understand it.
Without copying the final source, create a second small scenario that applies “Transactions and the Repository Boundary” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Integration-test the real repository against PostgreSQL so fake and implementation do not drift.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Repository wrapping every trivial Prisma call with no value
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.