Skip to content

Commit

Permalink
Merge pull request #219 from markus-gsf-seidl/feature/server-side-ren…
Browse files Browse the repository at this point in the history
…dering

Use server-side rendering for high-traffic pages
  • Loading branch information
russelltrow authored Oct 19, 2023
2 parents bdfdee9 + 171acac commit 73428fe
Showing 1 changed file with 45 additions and 0 deletions.
45 changes: 45 additions & 0 deletions docs/catalog/web/use-server-side-rendering.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
version: 1.0
submitted_by: markus-ntt-seidl
published_date: TBD
category: web
description:
tags:
- web
---

# Use server-side rendering for high-traffic pages

## Description

Modern web applications feature a lot of interface elements that are stored in templates on the server. This template is downloaded with the application code and then rendered with, optionally, requested data from the server.
This can dramatically increase the SCI in different scenarios: When the client device doesn't have access to green energy, when the page usage is short (for example: accidental clicks, pages with short dwell time like landing pages) or if a lot of server-round-trips are needed to gather data.


## Solution

Consider using server-side rendering as a method to reduce energy consumption on client side. Frameworks like Angular or React already provide solutions on how to implement this efficiently.
Server side rendering can improve side loading times (including rendering time on slower hardware), reduce network requirements (less round trips needed), can utilize caching (pre-rendered pages can be stored on the client device).

## SCI Impact

`SCI = (E * I) + M per R`
[Software Carbon Intensity Spec](https://grnsft.org/sci)

Server side rendering affects the SCI in the following aspects:

- `E`: Pre-rendering once can dramatically reduce energy consumption; pre-rendering on every request can reduce energy consumption if the server is more energy efficient and has access to green energy

## Assumptions

- Assumes that the used frontend technology allows for pre-rendered content
- Assumes that the web page is visited in high volume to affect the overall SCI impact

## Considerations

- Consider using a caching mechanism to store rendered pages, if they change frequently but still are met with a high load. This can significantly reduce the server load by serving pre-rendered content for frequent requests.
- Consider the other patterns in the web category

## References

- [Azure Well-Architected Framework Sustainability Pillar](https://learn.microsoft.com/en-us/azure/architecture/framework/sustainability/sustainability-application-design)

0 comments on commit 73428fe

Please sign in to comment.