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

Add a cache layer #33

Open
mrhappyasthma opened this issue May 16, 2021 · 2 comments
Open

Add a cache layer #33

mrhappyasthma opened this issue May 16, 2021 · 2 comments
Labels
enhancement New feature or request open question Further information is requested

Comments

@mrhappyasthma
Copy link
Owner

I need to determine a good TTL, but a cache layer might be nice for speed and to avoid external URL fetch costs.

Data updates, at most, once a quarter. So caching for week or maybe months at a time is probably pretty safe without losing much accuracy.
@mrhappyasthma
Copy link
Owner Author

The URL fetch quota on App Engine is more permissive than the new python3 datastore limits. So this may be infeasible while trying to ensure that I stay below the free budget thresholds using App Engine.

@mrhappyasthma mrhappyasthma added enhancement New feature or request open question Further information is requested labels Jun 10, 2021
@mrhappyasthma
Copy link
Owner Author

App Engine now longer has free budgets for this... But maybe it's still worth the investment to limit queries out to our data fetcher (i.e. MSNMoney).

Things like the Stock IDs or even general stock data could probably be cached for a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request open question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mrhappyasthma