server-side rendering
Building a page’s HTML on the server for each request, so the browser can show content before any JavaScript runs.
In more detail
Users see content sooner and search engines can read it without running scripts. The browser then loads JavaScript to make the page interactive.
Examples
The Next.js frontend is server-rendered and sits behind the Ingress on the root path.Code that behaves differently on server and client, such as reading window or random numbers during a React render, breaks hydration.Related terms
- Next.js — A React framework for building web applications that can render pages on the server and supports React Server Components.
- single-page application — A website that loads once and then updates its content with JavaScript instead of loading a new page for each view.
- streaming SSR — Server-side rendering that sends the HTML shell immediately and streams the rest of the page as each piece of data becomes ready.
- static rendering — Rendering a page to HTML once, at build time or on a schedule, and serving that same result to every visitor.
- hydration — The step where React in the browser attaches event handlers and state to HTML that was already rendered on the server.
- renderToStaticMarkup — A React DOM server function that renders a component tree to a plain HTML string, with no interactivity attached.
- progressive enhancement — Building a page that works everywhere first, then adding better features for browsers that support them.
Taught in
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Client Components: use client & Hydration Models — Next.js 15 & Modern App Router Architecture
- Component Tree Composition: Interleaving RSC & Client — Next.js 15 & Modern App Router Architecture
- Dynamic Routes: Slugs & generateStaticParams — Next.js 15 & Modern App Router Architecture
- Streaming SSR: Progressive HTML & Chunked Transfers — Next.js 15 & Modern App Router Architecture
- Metadata API: Dynamic OpenGraph & Head Management — Next.js 15 & Modern App Router Architecture
- Instrumentation: OpenTelemetry & Performance Spans — Next.js 15 & Modern App Router Architecture
- Component Purity: Pure Functions, Idempotence And Side Effects — React 19 & Modern Component Architecture
- useLayoutEffect vs useEffect: Painting And Synchronous Reads — React 19 & Modern Component Architecture
- useSyncExternalStore: Tearing-Free Store Subscriptions — React 19 & Modern Component Architecture
- useId: Generating Stable Accessible Form Element Identifiers — React 19 & Modern Component Architecture
- useActionState: Async Action Handlers And Pending States — React 19 & Modern Component Architecture
- Error Boundaries: componentDidCatch And Fallback UI Trees — React 19 & Modern Component Architecture