Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider switching from a server-side SWR implementation to Nginx caching #486

Open
muffinresearch opened this issue Feb 9, 2021 · 0 comments

Comments

@muffinresearch
Copy link
Contributor

muffinresearch commented Feb 9, 2021

Once the Next.js port has landed, since Nginx sits on top of the Next.js app on Heroku, it might be better to use that instead of a custom server-side implementation of SWR.

Nginx is able to handle serving stale content whilst refreshing the data in the background: See https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_use_stale and http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_background_update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant