terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity
next.js/examples/ssr-caching
History
Olivier Tassinari 2473b55871 [ssr-caching] Only cache 200 status requests (#3708) 
* [ssr-caching] Only cache 200 requests

I'm assuming caching an error page is a bad pattern.

* Update server.js
2018-02-06 17:51:49 +05:30
..
pages Add an example with SSR caching. (#497) 2016-12-23 09:13:52 -08:00
package.json Upgrade React for all examples (#3113) 2017-10-17 08:11:46 +02:00
README.md Use canary for all example downloads (#3411) 2017-12-06 18:12:42 -08:00
server.js [ssr-caching] Only cache 200 status requests (#3708) 2018-02-06 17:51:49 +05:30

README.md

Deploy to now

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

How to use

Using create-next-app

Download create-next-app to bootstrap the example:

npm i -g create-next-app
create-next-app --example ssr-caching ssr-caching-app

Download manually

Download the example or clone the repo:

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

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.