mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00

History

Peter Kellner c03d25b97a Added length calculation for insert of cache rather then default to 1… (#5835 ) * Added length calculation for insert of cache rather then default to 1. changed default cache from 100 to 100MB * adjusted for lint		2018-12-06 23:17:59 +01:00
..
pages	Add an example with SSR caching. (#497 )	2016-12-23 09:13:52 -08:00
package.json	Update ssr-caching example (#4363 )	2018-05-14 00:00:37 +02:00
README.md	#4751 - Explicitly mention install when cloning examples (#4758 )	2018-07-11 23:56:15 +02:00
server.js	Added length calculation for insert of cache rather then default to 1… (#5835 )	2018-12-06 23:17:59 +01: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.