When a Repository Earns Its Place Volume 07 - Advanced Application Architecture | Phase 24
The smell is not Prisma itself Prisma is already a strong type-safe data access API. Wrapping every single Prisma call with an identical method such as repository.findMany() usually adds no architectural value. The useful pressure appears when business services need to stop knowing detailed relation filters, pagination/count mechanics, persistence mapping, or testing setup.
Before the repository TasksService -> Prisma task.findMany(...deep authorization scope...) -> Prisma task.count(...same where...) -> Prisma error codes -> relation include/select shapes -> business rules -> workflow decisions
After a useful repository TasksService -> taskRepository.listScoped(userId, query) -> business rules -> workflow decisions
PrismaTaskRepository -> Prisma where/orderBy/select -> count + page query -> persistence mapping
Decision checklist • Would the service become easier to read if query construction moved out?
• Do multiple workflows need the same complex persistence query?
• Do unit tests currently need extensive Prisma-shaped mocks?
• Would a stable application-owned result type reduce persistence leakage?
• Can you name repository operations in business/persistence language more meaningful than generic CRUD?
When a Repository Earns Its Place 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 “When a Repository Earns Its Place” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: service intent → repository contract → adapter → Prisma/Postgres → domain 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: 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.
export interface TaskRepository {
findById(id: string): Promise<Task | null>;
listForWorkspace(input: TaskListQuery): Promise<TaskPage>;
save(task: Task): Promise<void>;
}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.
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 “When a Repository Earns Its Place” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Choose a service whose persistence queries are complex enough to justify a boundary.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.GenericRepository<T> mirroring ORM methods
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.