Server-Side Rendering (SSR) is a process where web pages or web applications are rendered on the server before being sent to the browser. In contrast to traditional client-side rendering (CSR), where the browser receives the code and handles the webpage's rendering, SSR involves a significant portion of rendering taking place on the server.
The process of Server-Side Rendering operates as follows:
Requesting a Web Page: When a user requests a web page, the browser sends a request to the server for the corresponding page.
Server-Side Rendering: The server receives the request, processes it, and renders the HTML page with all the necessary content and data.
Transmission to the Browser: The server sends the fully rendered HTML page to the user's browser.
Interactivity: Once the browser receives the HTML page, it displays it immediately while simultaneously loading JavaScript and CSS files. These files enable interactivity on the webpage by adding additional functionalities or enhancing the user experience.
The primary advantage of Server-Side Rendering lies in the quicker display of content to the user, as the browser receives a complete HTML page that can be displayed while other resources are loading. Additionally, SSR also offers benefits in terms of Search Engine Optimization (SEO) as search engines can better index the page's content when it's provided directly as HTML.
SSR is commonly used for complex web applications, content-centric pages, and pages that require better SEO performance. However, it's not always the best choice for every application, as it can cause additional server load and might not be necessary when an application primarily consists of interactive components that can be rendered on the client-side.
Erlang
