Scaling and Migration Without a Rewrite The TaskFlow architecture is intentionally replaceable. Scale the constrained boundary first, then extract only where independent operation creates more value than distributed-system cost.
- - - Selective - Cloud/on-prem Modular monolith Workers Read models > > > services > options
Typical evolution • Vercel web can remain independent while NestJS API/workers scale separately.
• Move long work to BullMQ workers before splitting business modules into network services.
• Supabase PostgreSQL can migrate to self-hosted/AWS PostgreSQL because Prisma/application services do not depend on dashboard-only business logic.
• Supabase Storage can migrate behind an application-owned storage adapter to S3-compatible storage; Redis/Upstash can move to self-hosted/managed Redis.
Service extraction trigger • Extract when a module needs independent scaling, release, resilience, compliance, or team ownership and has a stable contract/data boundary.
• After extraction, accept new costs: network failure, distributed tracing, eventual consistency, deployment coordination, contract versioning, and data ownership. Microservices are a trade, not an upgrade. A well-modularized monolith can support very serious systems. Source basis: Phase 35 dependency boundaries plus replaceable infrastructure strategy. Service extraction requires operational evidence.
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 “Scaling Migration and Service Extraction” 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: Enterprise expansion blueprint for an HRIS/procurement/inventory/payroll-style system with modules, workflows, events, audit, and scaling triggers.. 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 “Scaling Migration and Service Extraction” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Separate synchronous user requests from background work such as reports, imports, notifications, or payroll runs.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Dual writes to database and message broker without reliability design
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.