Level 4 · Master Architecture¶
Goal: make the decisions a senior or lead React engineer makes. At this level the questions are less "how do I use this hook?" and more "where should this code run?", "why is this interaction slow and how do I prove it?", "how do twelve people work in this codebase without stepping on each other?", and "what could an attacker do with this component?".
Modules¶
- Server Components & Frameworks — the server/client split,
'use client', Server Functions, and choosing a framework - Concurrent Rendering —
useTransition,useDeferredValue, and how interruptible rendering works - Performance Profiling — Core Web Vitals, the React Profiler, the Performance panel, and a repeatable method
- Design Systems & Component Libraries — tokens, headless primitives, variants, and documentation
- Architecture for Large Apps — feature-based structure, boundaries, and dependency rules
- Security in React Apps — XSS,
dangerouslySetInnerHTML, URLs, tokens, and supply chain - Testing Strategy — what to test at which level, end-to-end tests, and keeping suites fast and trustworthy
- Building & Deploying — static hosting, environment variables, caching, and CI
- Internationalization — translations, plurals,
Intlformatting and right-to-left layouts - Capstone — Team Dashboard — a production-grade app assembled from every level
Before you start¶
You should be fluent with everything in Levels 1–3. Several topics here depend on tools outside React itself — a meta-framework for Server Components, a hosting provider for deployment, a monitoring service for real-user metrics. Where something can't be fully run on a laptop alone, the lesson says so and shows what you can practise locally.
React's server-side features have been evolving quickly. This level teaches the concepts that hold across frameworks and points you to each framework's documentation for exact file conventions and configuration.