History

Joe Haddad 18a9c7e371 Improve linting rules to catch more errors (#9374 ) * Update `packages/` * Update examples * Update tests * Update bench * Update top level files * Fix build * trigger		2019-11-10 19:24:53 -08:00
..
pages	Improve linting rules to catch more errors (#9374 )	2019-11-10 19:24:53 -08:00
package.json	Move syntax formatting to prettier (#7454 )	2019-05-29 13:57:26 +02:00
README.md	Replace the deprecated Create Next App URL (#9032 )	2019-10-10 23:34:14 -04:00
server.js	Improve linting rules to catch more errors (#9374 )	2019-11-10 19:24:53 -08:00

README.md

Example app where it caches SSR'ed pages in the memory

How to use

Using `create-next-app`

Execute create-next-app with Yarn or npx to bootstrap the example:

npx create-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 now (download)

now

The idea behind the example

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.

Alternatively, see the example using React ESI.