DEV Community

Cover image for Client Side Rendering vs Server Side Rendering

Client Side Rendering vs Server Side Rendering

Akhila Ariyachandra on October 10, 2019

PS - This was originally posted on my blog. Check it out if you want learn more about React and JavaScript! You might have heard the terms Clien...
Collapse
 
prashantandani profile image
Prashant Andani • Edited

Hi Akhila,
In the below statement did you mean "Server" in the place of browser
"In a Universal Web App, the initial render will be done in the browser, and once the page loads client side rendering will take over."

Collapse
 
akhilaariyachandra profile image
Akhila Ariyachandra

Yes I meant server and just fixed it. Thanks for catching that!!! 😊

Collapse
 
wintercounter profile image
Victor Vincent

My disadvantages against SSR:

  • Higher costs for backend infrastructure.
  • Many workarounds are necessary.
  • 3rd party tools not supporting.

I wouldn't say "have to wait a long time", it's simply not true. Usually the overhead is not bigger than ~200ms for static pages. The issue comes when you need extra API calls to construct your page, but even that case can be handled by injecting the initial responses into your index.html. It's a much cheaper solution and you don't need Node for it.

For SEO there is Prerender.io and similar solutions.

Collapse
 
Sloan, the sloth mascot
Comment deleted
Collapse
 
wintercounter profile image
Victor Vincent

What do you mean?

Collapse
 
codegenty profile image
Emekus

browser caching.

Thread Thread
 
wintercounter profile image
Victor Vincent

Yes, I mean by that what you mean? :) What's the problem with CSR regarding browser caching?

Collapse
 
elmuerte profile image
Michiel Hendriks

When I started webdevelopment I did Developer Side Rendering. This will be the next step ;)