liveBook · Manning

Universal rendering

As explained in Vanilla Web

Universal rendering is an architecture that renders initial HTML on the server and then enables client-side interactivity through hydration.

Universal rendering combines server-side rendering (SSR) and client-side rendering (CSR). The server produces the initial HTML; client-side code then hydrates it and takes over interactivity. It is also called isomorphic rendering, hybrid rendering, or SSR with hydration. section 2.1.4

Unlike SSR alone or CSR alone, this approach needs technology that runs on both server and client, such as JavaScript. It also needs backend technology tightly integrated with the client. Managing the build and serving process adds complexity, so it is a natural fit for frameworks and less common in a pure vanilla approach. Next.js and Angular’s built-in SSR are examples. section 2.1.4

How Vanilla Web covers it

How deep it goes
Defines server rendering and client hydration, then identifies integration costs without giving implementation steps.
Examples
Names Next.js and Angular’s built-in SSR as implementations without working through an application.
What you can do after
Evaluate/understand it as an architectural option with integrated backend, build, and serving requirements.
How it connects
Connects server-side rendering, client-side rendering, hydration, and JavaScript frameworks.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vanilla Web. The section links point to the parts of the book it draws on.