SSR (Server-Side Rendering)
prepares rendering on the server side and delivers it to the client in response to the initial request, which is a way to display HTML that is already rendered on the entire browser's screen.
(A method of rendering html to clients after rendering dynamically changing sites such as JSP or PHP)
CSR(Client-Side Rendering)A client request is made on the initial client screen, JavaScript.(A method of providing empty index.html files and js files to clients and rendering them in the browser with those files)
(Vue,React)
<
SSG(Static Site Generation)
SG(Static Site Generation)precompiles and distributes files to a JavaScript file. Unless the content of the site changes, it does not import dynamic data on client requests, but only provides static files. This can speed up page loading and increase security.
(Just providing rendered html on server)
(Nuxt, common static web page)
Difference between SSR and CSRWeb page loading time: SSR is fast at initial loading, but CSR is slow after loading.
SEO Response: SSR is advantageous for search engine optimization, and CSR may be vulnerable to SEO because it requires JavaScript execution initially.
Using server resources: SSR uses more server resources, CSR uses more client resources.
Summary: SSR has a fast initial loading time and is advantageous for SEO, and CSR is useful when there is a lot of dynamic interaction. Your choice depends on the nature and requirements of your web application.
The screen flashes because SSR receives pages every time it requests, but CSR renders pages a little slower at the beginning and then renders them on the client, so the flow of requests
SSR
.(A method of providing empty index.html files and js files to clients and rendering them in the browser with those files)
(Vue,React)
<
SSG(Static Site Generation)
SG(Static Site Generation)precompiles and distributes files to a JavaScript file. Unless the content of the site changes, it does not import dynamic data on client requests, but only provides static files. This can speed up page loading and increase security.
(Just providing rendered html on server)
(Nuxt, common static web page)
Difference between SSR and CSRWeb page loading time: SSR is fast at initial loading, but CSR is slow after loading.
SEO Response: SSR is advantageous for search engine optimization, and CSR may be vulnerable to SEO because it requires JavaScript execution initially.
Using server resources: SSR uses more server resources, CSR uses more client resources.
Summary: SSR has a fast initial loading time and is advantageous for SEO, and CSR is useful when there is a lot of dynamic interaction. Your choice depends on the nature and requirements of your web application.
The screen flashes because SSR receives pages every time it requests, but CSR renders pages a little slower at the beginning and then renders them on the client, so the flow of requests
Web page loading time: SSR is fast at initial loading, but CSR is slow after loading.
Web page loading time: SSR is fast at initial loading, but CSR is slow after loading.
SEO Response: SSR is advantageous for search engine optimization, and CSR may be vulnerable to SEO because it requires JavaScript execution initially.
Using server resources: SSR uses more server resources, CSR uses more client resources.
SSR
Nuxt generates the JS source code with the build command. After rendering the file in express (WAS), the framework of nodejs, the rendered html is returned to the browser (SSR) Nuxt can also generate an html file rendered with the generate command. When the file is placed on the web server, it returns the rendered html to the browser (SSG)