Member-only story
Client-Side Rendering vs. Server-Side Rendering vs. Pre-rendering
This article was originally published at https://www.blog.duomly.com/client-side-rendering-vs-server-side-rendering-vs-prerendering/
Intro to Client-Side Rendering vs. Server-Side Rendering
We can create awesome web applications and websites with the technologies we have right now, but there’s still a performance that needs to be considered. Developers outdo each other to achieve the best results in loading speed and user experience in their projects. And at that point, there are many discussions on the way, applications should be rendered.
Before modern front-end frameworks started to be used so commonly, websites were rendered on the server, and ready .html files were sent to the browser.
When developers started using ReactJS or Angular, web pages started to be rendered in the browser. Then again, to make loading faster and user experience better, frameworks for server-side rendering, like Next.js, started to be more popular.
And there’s also a pre-rendering, which is another approach for rendering a web application. But which one will be best for your next project?
In this article, I’d like to go through those three concepts, client-side rendering, server-side…
