|1) Server Side Rendering|
|2) Client Side Rendering|
|3) Universal Rendering|
|4) Static Rendering|
Sometimes it might be hard to understand the differences between the different web rendering solutions. If you're a web developer, you've probably heard these words:
- Server Side Rendering (SSR)
- Client Side Rendering (CSR)
- Universal Rendering (sometimes simplified to "SSR")
- Static Rendering (or JAMStack depending on the tool you're using)
Here are 4 videos explaining in a simplified manner the process of each solution from a user's perspective. Know that the user scenario is the exact same in the 4 videos.
In the last section you'll find a comparison listing benefits and drawbacks of each solution.
Server Side Rendering (SSR)
⚠️ Note: Here I'm talking about full server side rendered websites (you know, old SSR websites 😉). This architecture was widely used before Single Page Apps were introduced.
Client Side Rendering (CSR)
Frameworks using CSR: Vue, React, Angular
Frameworks using Universal Rendering: Nuxt.js, Next.js, Angular Universal
Frameworks/Tools using Static Rendering: Gatsby, VuePress, Gridsome, Next.js, Hugo, Jekyll
|Server Side Rendering||Client Side Rendering||Universal Rendering||Static Rendering|
|Fast initial load to show the full content of the page||⚡️⚡️||⚡️||⚡️⚡️||⚡️⚡️⚡️|
|Full page reload when navigating||yes||no||no||it depends on the tool you're using|
|Requires server hosting||yes||no||yes||no|
|Fluid seamless user experience on page navigation||👎||👍||👍||👍|
|Integrates well with websites based on frequent/real-time updates||👍||👍||👍||😕|
Feel free to contact me on twitter if you have questions!
Top comments (27)
This is an okay high-level introduction, but I feel like it's an oversimplification that buys too much into current dogma about web development and which might give folks the wrong idea, especially with the characteristics matrix at the very end.
Not all server side rendering things use a REST API under the hood, for example (WordPress is a common example of this), and I'm not sure what you mean by a "fluid seamless user experience" that is necessarily made impossible by server-side rendering (at least, in a way that is still universally allowed by static rendering).
There is still plenty of room for traditional server-side rendering on the web; not everything has to be "an app."
As mentionned in the intro, everything is explained in a "simplified manner" which means that concepts are voluntarily simplified for pedagogy reasons. This article exposes the most important concepts of web rendering.
I think people are smart enough to understand that REST API can be replaced by whatever you want. (btw you're talking about WordPress, but the data you're getting from WordPress is from a REST API) I used REST API as an example because it is the most common way to handle dynamic data.
By "fluid seamless user experience" I mean the time it takes to display a new page during the in-app navigation, which is fast for static, universal and csr, but not for ssr. (I give you this point, I'll update the description as it's not clear).
Web rendering is something really complex. For example, I could have divided static rendering in several subcategories, because each tool works in a different way. However, the overall idea is the same, and this is what I want to show in this article.
Sometimes, simplification is the best way to teach people, and they don't need to know the exact behavior under the hood.
If you're interested in having a more advanced vision of these concepts, I highly recommend you to read this.
The fact that WordPress provides a REST API doesn't mean that its rendering stack uses that internally for its actual rendering. Maybe they've changed that in recent years but last I checked, it's pulling the data directly out of the database when it's doing its own rendering frontend.
My issue with the characterization provided in your animation is that it implies that all server-side rendering works in that way, and that the resulting rendering is going to also be slow as an unavoidable result of that, when neither aspect is true. Even if it's going through a REST API, if it's connecting to itself on the same host it'll be quite a lot faster than what's implied by the additional backend connections.
Basically I feel like in your effort to simplify the explanation of these different things you've actually added more complexity to a situation, by implying that things need to be more complex than they actually are.
Maybe I'm just a curmudgeon for disliking the way that websites-as-apps have taken over everyone's way of thinking though. I like to keep things simple, and have never cared for the artificial split between frontend/backend/full-stack for that matter.
I think that you're misunderstanding here...
I'll repeat myself: I used this architecture as an example as it is the most common architecture nowadays and it was easier to explain the concepts this way.
"I feel like in your effort to simplify the explanation of these different things you've actually added more complexity" : That's your point of view.
Reacting on something fluffy said:
I don't agree that the split is artificial at all. It's actually eminently practical to decorrelate presentation from data.
While you're perfectly accurate when you point out that 'old-style' SSR (i.e. Rails, etc.) doesn't necessarily follow the API pattern and pulls data straight from data sources (esp. databases), it's not a pattern I would recommend nowadays, where you might have multiple frontend data 'consumers' (website(s), phone apps, desktop apps, other APIs) for a single data 'provider' (your API, which is really a data aggregator, as you might be pulling data from a variety of sources).
With a monolithic design pattern, you would have to replicate the backend side for each consumer frontend. Admittedly, you could engineer your monolithic design to return, say, JSON as well as HTML and thus turn it into an API in addition to being a website, but that muddles up the whole idea of separation of concerns between data and presentation, which is the opposite of "keeping things simple" as you put it.
These animations are way too good. Thank you for this!
Also, while Turbolinks ships standard with Rails, any SSR framework developer can use it to achieve lightning fast page navigation without server round-trips.
Hello! What a nice article! It helped me a lot to understand diverse rendering processes. Would you mind if I translate this in Korean with link to original source and post on my blog? I will leave the link after posting. I will wait for your response :)
Animations are top-notch 💯
I love the animations and the chart at the bottom. It's crazy because all of this happens within seconds (most of the time lol) but there is still always something faster.
Thanks. Animation is perfect
Nice animations and explanation, how do you make these ?
Thanks ! I used keynote 🙂
wow, thanks sir.
This came in just in time of me starting the process of picking a frontend stack. Thanks for a simpler explanation, think I may actually use universal rendering now 😉
Happy that it helped you made your decisions !
This is a huge help for my understanding of all these types of rendering. Thank you 🙏 I do appreciate the final comparisons table.
I'm really happy that it helped you 😊
What about solutions like StimulusReflex and Phoenix LiveView that can deliver highly performant reactive UIs faster than an SPA?
It seems like the existence of StimulusReflex raises the valid question of whether we need these heavy JS frameworks at all.
simple animation with lots of information. Thank you
You're welcome !