When or how do you know which to choose between CSR and SSR ?

Often times, we found ourselves in a situation to decide what tech stack or development methodolgy will favour our product. This is a question most people ask.

please share your view on this topic...

Comments

[Ben Halpern]

• What is most important for UX, accessibility, and perhaps stuff like SEO? Some projects have demands that require one or the other
• What does the framework make easy? Often the right choice is whatever isn't fighting the good parts of the ecosystem you're working in.
• What are the short term and long term requirements of the project? Is the choice I'm making now the "forever" choice? (And be honest about the possibility of that).

[Makanju Oluwafemi]

Thanks Ben, I preety much appreciate your response. However, what i do think is, companies could use these two methodology together. but knowing where they belong at every stages of the app is important. for example.... any app that lives behind login should be restricted to csr with exceptions to blog and some site that requires heavy seo.

just basically prioritising SEO

[Alex Lohr]

I would take the second suggestion with a grain of salt: choosing the patterns you want to solve your issues with after the framework instead of the problem is like the tail wagging the dog.

[Alex Lohr]

It really depends on the problem you aim to solve. Maybe there are even two of them, one a landing page and another the highly interactive app that requires a login. The former should be SSR or even static SSG, the latter CSR.

[Makanju Oluwafemi]

I totally agree

[Makanju Oluwafemi]

Thanks Alex