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

Cache travel time results #171

Merged
merged 7 commits into from
Dec 17, 2024
Merged

Cache travel time results #171

merged 7 commits into from
Dec 17, 2024

Conversation

Nate-Wessel
Copy link
Contributor

Cache would only only be used for the exact same request on the same version of the app

temporarily in personal schema for ease of testing
trading space for speed in setting this up, for now
@Nate-Wessel Nate-Wessel self-assigned this Dec 13, 2024
@Nate-Wessel
Copy link
Contributor Author

Cache lookup is being done. Just need to actually store new values now.

@Nate-Wessel
Copy link
Contributor Author

Cache is storing values.

Next step it to more loosely couple this with the database. I'd like to do a try/catch in case anything goes wrong with access the cache table it should silently fall back to just not caching.

just in case something ever breaks, I don't want to be dependent on caching
@Nate-Wessel Nate-Wessel marked this pull request as ready for review December 17, 2024 19:55
@Nate-Wessel Nate-Wessel merged commit 6fc11be into deploy Dec 17, 2024
1 check passed
@Nate-Wessel Nate-Wessel deleted the cache-results branch December 17, 2024 19:57
@Nate-Wessel Nate-Wessel linked an issue Dec 17, 2024 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cache travel time results in the database
1 participant