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

Edge caching #7

Open
lfborjas opened this issue Aug 24, 2020 · 2 comments
Open

Edge caching #7

lfborjas opened this issue Aug 24, 2020 · 2 comments
Labels
enhancement New feature or request icebox Features for the distant future

Comments

@lfborjas
Copy link
Owner

Probably want something like this: https://devcenter.heroku.com/articles/edge -- $5 a month, but should keep things snappy.

@lfborjas lfborjas added the enhancement New feature or request label Sep 2, 2020
@lfborjas lfborjas changed the title Edge caching Edge caching, SSL, faster dynos Oct 18, 2020
@lfborjas
Copy link
Owner Author

All of these features are paid. Consider adding a sponsorship option? https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository

@lfborjas lfborjas changed the title Edge caching, SSL, faster dynos Edge caching Oct 20, 2020
@lfborjas
Copy link
Owner Author

In fact, apart from static assets (which are very tiny right now,) edge caching would probably be as useful as simple browser caching for the current set of features: how often are people looking at their own chart in different devices? Maybe they're linking it from their websites? I believe client-side simple caching (as per #23 ) will get us a long way, and if there's enough traffic to warrant edge caching, maybe Fastly or Google Cloud CDN are better options?

@lfborjas lfborjas added the icebox Features for the distant future label Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request icebox Features for the distant future
Projects
None yet
Development

No branches or pull requests

1 participant