Prerendering: running a client-side application at build time to capture its initial state as static HTML.Rehydration: “booting up” JavaScript views on the client such that they reuse the server-rendered HTML’s DOM tree and data.CSR: Client-Side Rendering - rendering an app in a browser, generally using the DOM.SSR: Server-Side Rendering - rendering a client-side or universal app to HTML on the server.The differences between these approaches help illustrate the trade-offs of rendering on the web through the lens of performance. In order to better understand the architectures we’re choosing from when we make this decision, we need to have a solid understanding of each approach and consistent terminology to use when speaking about them. Broadly speaking, we would encourage developers to consider server rendering or static rendering over a full rehydration approach. Our understanding of this space is informed by our work in Chrome talking to large sites over the past few years. This can be difficult, since there are a number of different ways to build a website. One of the core decisions web developers must make is where to implement logic and rendering in their application. Streaming server rendering and Progressive RehydrationĪs developers, we are often faced with decisions that will affect the entire architecture of our applications.A Rehydration Problem: One App for the Price of Two.Combining server rendering and CSR via rehydration.

Universal media server roku renderer