Server-side rendering
Server-side rendering produces HTML on the server. Freshness, personalisation and speed also depend on data access and caching.
Produce HTML on the server
Server-side rendering, or SSR, means generating HTML content on the server and sending it to the browser. In projects, SSR often refers to generation when a page is requested. The browser may then handle further interactions.
In a fictional order view, the server checks access and produces a page containing the signed-in person's orders. If that output is cached, it must not accidentally be served to other people. Choosing SSR does not automatically resolve access and cache rules.
Static site generation instead creates HTML in advance during a build step. This also happens outside the browser and may count as server-side generation in a broad sense. Planning therefore needs the actual generation time, required data and later update process, rather than the abbreviation alone.
Sources
Related terms
- Static site generationStatic site generation creates pages as files in advance. Changes to source data must also reach the output served to users.
- HydrationHydration connects existing browser HTML with its application logic. Visible content and working interaction require separate checks.
- BackendThe backend handles an application’s server-side rules and data. It is more than a database or an administration screen.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps