You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: