Full-Stack Patterns & Architecture covers: The Next.js Handbook, Programming JavaScript Applications, Learning React Native. Master full-stack JavaScript architecture — Next.js (SSR/SSG/ISR), API design patterns, monorepo structure, state management at scale, and the architectural decisions that make or break large frontend applications.
Next.js is the React world's answer to Rails. File-based routing (app/users/page.tsx) is like config/routes.rb but using the filesystem. Server components are like Rails views — they render on the server with direct database access. API routes (app/api/users/route.ts) are like Rails controllers. getServerSideProps is like a Rails controller action that fetches data before rendering. The key difference: Next.js gives you SSR, SSG, and ISR in one framework, while Rails only does SSR. But Rails has Active Record, Action Mailer, Active Job, and the entire ecosystem. Next.js has the React ecosystem. The "right" choice depends on the problem.
This course unlocks once you've finished its prerequisite. Open prerequisite →
Next.js is the Rails of React. I mean this literally. Opinionated file-based routing. Built-in API routes. Server-side rendering by default. Image optimization, middleware, enviro…
Somewhere in the React world, around 2016, engineers started rediscovering things you already know. That rendering HTML on a server is fast. That file conventions beat configurati…
Rails answered your architecture questions before you ever asked them. Where does business logic live? Models. Where do request handlers go? Controllers. Where's the config? confi…
Here's a question worth sitting with: when you learned React in Course 4, what exactly did you learn? If your answer is "how to build web UIs," React Native is about to surprise y…
Work through each item before the checkpoint.
Next.js App Router with the full-stack pattern set: server components reading Prisma directly, route handlers with honest status codes, server actions validating FormData, and an …
6 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.