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

Hydrate facility_data in cache on startup #749

Open
Maelstromeous opened this issue Apr 28, 2023 · 0 comments
Open

Hydrate facility_data in cache on startup #749

Maelstromeous opened this issue Apr 28, 2023 · 0 comments

Comments

@Maelstromeous
Copy link
Member

There's little point in not having the facility data in cache upon startup. This could be easily done by grabbing the latest lattice from the PS2A API, then doing a query to Census to pull in that facility data, and store it in Redis.

The TTL for this data should be set to a long duration, since facilites very rarely change. It could also be namespaced by lattice version, therefore whenever our lattice versions update, we instantly invalidate the cache as it needs a new set of data.

Recommended TTL should be 72 hours / 3 days.

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