✳flâneur — a map of the web's best reading

Rendering on the Web | Articles | web.dev

web.dev · 2,701 words · saved by 1 readers

Where should we implement logic and rendering in our applications? Should we use Server Side Rendering? What about Rehydration? Let's find some answers! As developers, we are often faced with decisions that will affect the entire architecture of our applications. One of the core decisions web developers must make is where to implement logic and rendering in their application. This can be difficult, since there are a number of different ways to build a website. Our understanding of this space is informed by our work in Chrome talking to large sites over the past few years. Broadly speaking, we would encourage developers to consider server-side rendering or static rendering over a full rehydration approach. 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. The differences between these approaches help illustrate the trade-offs of

Home Articles Rendering on the Web Stay organized with collections Save and categorize content based on your preferences. Addy Osmani Jason Miller Published: February 6, 2019, Last updated: January 5, 2026 One of the core decisions web developers must make is where to implement logic and rendering in their application. This can be difficult because there are so many ways to build a website. Our understanding of this space is informed by our work in Chrome talking to large sites over the past few years. Broadly speaking, we encourage developers to consider server-side rendering or static render

Explore this link on the map →

related reading