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.

Sign up for GitHub

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

Jump to bottom

/routes proxy and cleanup #133

Closed
exxonvaldez opened this issue Jun 16, 2019 · 1 comment
Closed

/routes proxy and cleanup #133

exxonvaldez opened this issue Jun 16, 2019 · 1 comment

Comments

@exxonvaldez
Copy link
Contributor

exxonvaldez commented Jun 16, 2019 •
edited
Loading

As Jesse suggested in #132 : For production, we should probably have nginx in front of flask to gzip and cache responses to reduce bandwidth and reduce load on the flask backend. Don't need to implement that now though. Vickie H also suggests Envoy (https://www.loggly.com/blog/benchmarking-5-popular-load-balancers-nginx-haproxy-envoy-traefik-and-alb/)

Also, if the changes for #132 have no issues and can become permanent, then there is some refactoring and cleanup as described there. Can clone this issue as desired for that.
@exxonvaldez exxonvaldez mentioned this issue Jun 16, 2019
Merged
@youngj
Copy link
Contributor

youngj commented Jun 17, 2019

We could also consider using a CDN like AWS Cloudfront or Cloudflare for caching and compression.

@youngj youngj closed this as completed Jul 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@youngj @exxonvaldez