FULL_STACK_DEVELOPER_2026_COMPLETE - Phase 06 From Two Apps to One System
From Two Apps to One System Execution environments, network paths and the first full-stack mental model
Phase 06 turns two working applications into one full-stack system.
http://localhost:3000 apps/web http://localhost:4000
Later phases replace in-memory Todos with Prisma + PostgreSQL.
Figure - TaskFlow Phase 06 architecture. The browser sees Next.js on port 3000 while the independent NestJS API listens on port 4000.
FULL_STACK_DEVELOPER_2026_COMPLETE - Phase 06 From Two Apps to One System
Two working applications are not automatically one system At the end of Phase 05, the browser can render Next.js and PowerShell can call NestJS. That proves both halves work, but the product still has a missing link: the frontend has not consumed the backend contract. Phase 06 creates that link deliberately.
Phase 06 turns two working applications into one full-stack system.
http://localhost:3000 apps/web http://localhost:4000
Later phases replace in-memory Todos with Prisma + PostgreSQL.
Figure - TaskFlow Phase 06 architecture. The browser sees Next.js on port 3000 while the independent NestJS API listens on port 4000.
Where fetch executes changes the architecture Same API URL, different execution environment.
renders page / runs client JS Server Components port 4000
browser JavaScript
CORS is a browser security policy. A server-to-server fetch is not blocked by the browser CORS enforcement model.
Figure - Server Component fetch versus browser Client Component fetch. Knowing where code executes explains when CORS becomes relevant.
In the App Router, a Server Component can await fetch directly. That request originates from the Next.js server process. A Client Component runs JavaScript in the browser after hydration; its fetch originates from the browser. Both can target the same NestJS URL, but the security and observability characteristics differ.
FULL_STACK_DEVELOPER_2026_COMPLETE - Phase 06 From Two Apps to One System
Server-side request path Mental model
Browser-side request path Mental model
Why both are worth learning Dimension Server Component fetch Client Component fetch
Can read server-only env? Yes No
Subject to browser CORS No Yes enforcement?
Useful for Initial page data, server rendering Interactive refresh/mutations
Visible in browser Network Usually no - browser requests Next.js page Yes as direct API call?
The course is not saying all reads must be server-side or all mutations must be client-side. The point is to understand the execution environment first. Later architecture decisions can then be made intentionally.
The browser is not the Next.js server This distinction becomes one of the most important full-stack debugging skills. If a server-side fetch fails, browser CORS settings are irrelevant. If a browser-side fetch is blocked by CORS, changing Prisma or React rendering will not fix it. Always identify where the failing code executed.
Official source notes Primary framework references: Next.js App Router Fetching Data and fetch API documentation; Next.js Environment Variables documentation; NestJS CORS documentation. Browser protocol references: MDN CORS, preflight request, and Fetch API documentation.
The course remains version-locked to the versions established in Phase 00. These sources are used to verify concepts and current API behavior, not to silently upgrade the course midstream.
From Two Apps to One System 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 Two Apps to One System” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: Next.js UI → typed request → NestJS endpoint → service → response state. 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: A typed API client boundary that can call the NestJS health/tasks endpoints from the appropriate Next.js execution context.. 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.
Input -> owner -> transformation -> observable output -> failure evidenceDo 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 Two Apps to One System” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Define API base URLs per environment instead of hard-coding localhost throughout components.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Using the browser-only URL from server-to-server code in deployment
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.