Server-Side Rendering
Subject: Computer and Technology noun /ˈsɜːr.vərˌsaɪd ˈrɛn.dər.ɪŋ/ 1 definition
- web-development
- web-architecture
- web-performance
- html-rendering
-
Definition (noun)
Entry #95 · UpdatedServer-Side Rendering (SSR) is a web architecture technique in which a web server processes application code, fetches required data, and constructs complete HTML markup for a requested route before transmitting the response to the client browser. Because the browser receives ready-to-parse HTML rather than an empty document shell that depends on JavaScript execution to build the DOM, SSR accelerates initial content display and enables search engine crawlers and link-preview bots to read page content reliably. Unlike Client-Side Rendering (CSR), which delegates UI assembly to browser-side scripts, or Static Site Generation (SSG), which pre-builds pages at deploy time, SSR generates markup dynamically per request and often pairs with client-side hydration to support rich interactivity.
Common Forms
Traditional Template SSR: Renders complete HTML on the backend using server-side template engines (such as Jinja, ERB, or Blade), keeping routing and state on the server without shipping a client-side application framework.
Isomorphic (Hydrated) SSR: Executes the same component-based JavaScript codebase (such as React, Vue, or Svelte) on both server and client, delivering initial HTML immediately and then attaching browser event listeners during hydration.
Streaming SSR: Transmits the HTML response incrementally in chunks over an open HTTP stream so the browser can paint layout shells and high-priority content while slower asynchronous data queries finish resolving.
Edge SSR: Runs server-rendering logic on distributed Content Delivery Network (CDN) edge nodes geographically close to end users rather than a centralized origin server, reducing network round-trip latency for dynamic pages.
Example
When a shopper requests
https://shop.example.com/items/482on an e-commerce platform, the Node.js application server queries the inventory database for live pricing and stock levels and responds with a complete HTML document containing the product details and Open Graph metadata. The browser displays the page contents immediately on arrival, and a client script hydrates the "Add to Cart" button moments later to enable interactive state updates.