VSF Cache NGINX

It does not require NGINX Plus

By default VSF is able to cache SSR Output in the Redis Cache. This module will Cache Redis Output in the NGINX. So Node.js server is not being used even to load output from Redis. It makes our app's first load even faster!

Example Category's view response time: 1920ms
Example Category's view response time with NGINX: 16ms

I've given same response time for both Varnish and Nginx as they are really similar. In my example config - default.conf, I also added basic gzip compression. Response times are without HTML minifier - in development mode. So in production it should be even faster.

How to install

To config's main section add:

"nginx": {
  "enabled": true,
  "bypassKey": "ad3489sf545824893289dfsdfsd",
  "host": "localhost",
  "port": 80,
  "protocol": "http",
  "bypassTimeOffset": 500
}

Obviously, set proper host and port if you are on production. You should also enable those 2 values in server section:

"useOutputCacheTagging": true,
"useOutputCache": true

Purge request will be send by Node server to Nginx. So if you are using k8s and one machine you probably want to send it via HTTP (without unnecessary TSL).

bypassKey - is value that tells Nginx that request is allowed to refresh cache. You should set it to equal this value in Nginx's config:

set $secret_key "ad3489sf545824893289dfsdfsd";

bypassTimeOffset - time in miliseconds that app will wait after each Bypass request, by default it is 500ms. But you should find the best one for yourself.

Now you need to apply purge-config loader to your app. Your config will be exposed in page's source or produced by Webpack - app.js. We cannot allow that because someone might use this data to purging your cache all the time! To prevent this merge this PR to your project: vuestorefront/vue-storefront#4540

It is important to put in your config:

"purgeConfig": [
    "server.invalidateCacheKey",
    "server.invalidateCacheForwardUrl",
    "server.trace",
    "redis",
    "install",
    "expireHeaders",
    "fastly",
    "nginx",
    "varnish"
  ]

This array tells app which parts of config should be available only server side! Presented values will be very good base in most cases.

Why do we wait between purge requests?

For real, free version of Nginx allows us only to use proxy_cache_bypass. If we set this to 1 - the request will go to the origin and update our cache. So what we do?:

Purge Cache in Redis
Send request to our App with proxy_cache_bypass == 1
Now our request will reach our PWA Node server. So if we would not wait between requests. For a few thousands of URLs to refresh, we could just DDoS our server... To prevent that, after each direct request to Node server, it will wait bypassTimeOffset amount of time.

Well... as we use Promise.all. We are resolving 2 promises in paralell and after each of them we waits bypassTimeOffset amount of time - then we send next one...

How to test it locally

Run app with docker-compose up
Run Nginx with docker-compose -f src/modules/vsf-cache-nginx/docker-compose.nginx.yml up
On port :80, you should have Cached with Nginx App. On port :3000 you should have Cached with Redis App.

It is important to have running Redis in same network. As it is essential for our Nginx cache (same for Varnish option).

How to purge cache?

When we purge Redis' cache. It will also purge Nginx's cache. So just open:

http://localhost:3000/invalidate?key=aeSu7aip&tag=*

Or:

http://yourNginxApp/invalidate?key=aeSu7aip&tag=*

Do I need NGINX Plus?

No. It was important for me to make it work with free version.

Caching does not work

Make sure you have this bugfix in your PWA: vuestorefront/vue-storefront#4143

Invalidate * does not work for category/product

Make sure it is fixed: vuestorefront/vue-storefront#4173

Does it work with Fastly?

I did not anything for that. So probably not. Feel free to prepare PR for that!

Errors

Are you getting?:

app_1  | [ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
app_1  |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1106:14)

It means you do not have running Redis' instance. The easiest solution that I've prepared for you will be run docker-compose with redis:

docker-compose -f src/modules/vsf-cache-nginx/docker-compose.redis.yml up

Kidl / vsf-cache-nginx