Server-side rendering (SSR)
What is SSR?
Server side rendering is an application’s ability to convert HTML files on the server into a fully rendered HTML page for the client. The web browser submits a request for information from the server, which instantly responds by sending a fully rendered page to the client.
What is server-side and client-side rendering?
SSR – rendering a client-side or universal app to HTML on the server. CSR: Client-Side Rendering – rendering an app in a browser, generally using the DOM. Rehydration: “booting up” JavaScript views on the client such that they reuse the server-rendered HTML’s DOM tree and data.
What is the meaning of server-side?
Much like with client side, ‘server side’ means everything that happens on the server, instead of on the client. In the past, nearly all business logic ran on the server side, and this included rendering dynamic webpages, interacting with databases, identity authentication, and push notifications.
What does server-side rendering mean in React?
SSR with JavaScript libraries like React is where the server returns a ready to render HTML page and the JS scripts required to make the page interactive. The HTML is rendered immediately with all the static elements.
What is difference between SSR and CSR?
The main difference between CSR and SSR is where the page is rendered. SSR renders the page on the server-side and CSR renders the page on the client-side. The client-side dynamically manages the routing without refreshing the page each time the client requests another route.
