> For the complete documentation index, see [llms.txt](https://justin-se.gitbook.io/justin-se-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://justin-se.gitbook.io/justin-se-docs/front-end-development/frontend-engineering/redering-method.md).

# Redering Method

## Static Site Generate (SSG)

generate static web page on build time.

**Pros :** 

* fast to load, no compute time needed.
* Cacheable, cached on client side, CDN server etc, could reduce compute & network load.

**Cons :** 

* every change need to rebuild.

***

## Server Side Render (SSR)

Every request will go into application to render the context. 

**Pros :** 

* Dynamic rendering, content can be up to date.
* SEO friendly

**Cons :** 

* slower to load, every request need time to compute.
* High server load, if there is 10k request will render 10k times.

***

## Incremental Static Regeneration (ISR)

in short, SSG with expire time.\
combination of SSG & SSR, server will generate static page with expire time, after expire will regenerate the page with SSR method.

**Pros :** 

* Have Advantage of SSG load speed & fresh content of SSR.
* Significant lower server load than SSR, since it only render once to serve multiple request. 
* SEO friendly.

**Cons :** 

* Not absolute up to date, sometime will have outdated content before it re-render.

***

## Client Side Render (CSR)

*