0b9475624f
This issue is related to #12964 **I changed the following examples:** `with-zeit-fetch` `with-why-did-you-render` `with-styletron` `custom-server-fastify` `custom-server-express` `with-why-did-you-render` `custom-server-hapi` `custom-server-koa` `custom-server-polka` `custom-server-typescript` `progressive-render` `ssr-caching` `svg-components` `using-preact` `with-ant-design` |
||
|---|---|---|
| .. | ||
| pages | ||
| package.json | ||
| README.md | ||
| server.js | ||
Example app where it caches SSR'ed pages in the memory
React Server Side rendering is very costly and takes a lot of server's CPU power for that. One of the best solutions for this problem is cache already rendered pages. That's what this example demonstrate.
This app uses Next's custom server and routing mode. It also uses express to handle routing and page serving.
How to use
Using create-next-app
Execute create-next-app with npm or Yarn to bootstrap the example:
npm init next-app --example ssr-caching ssr-caching-app
# or
yarn create next-app --example ssr-caching ssr-caching-app
Download manually
Download the example:
curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/ssr-caching
cd ssr-caching
Install it and run:
npm install
npm run dev
# or
yarn
yarn dev
Deploy it to the cloud with Vercel (Documentation).