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

would be more efficient to cache the user on the first call #10

Open
mattbonnell opened this issue May 23, 2020 · 0 comments
Open

would be more efficient to cache the user on the first call #10

mattbonnell opened this issue May 23, 2020 · 0 comments
Assignees
@mattbonnell
Labels
enhancement New feature or request infra Pertains to the app's infrastructure

Comments

@mattbonnell
Copy link
Contributor

mattbonnell commented May 23, 2020 •
edited
Loading

General

We should cache the user on the first call to auth.GetUser.
One possible key would be the user id.

Cache invalidation

Cache invalidation should occur when a user updated message is consumed. the updated user should then be stored in the cache.

https://github.com/safe-distance/spatium-infra/blob/d19a3de76935afab7efddcfc14776af88f7baecf/auth/auth.go#L54
@mattbonnell mattbonnell self-assigned this May 23, 2020
@mattbonnell mattbonnell added enhancement New feature or request infra Pertains to the app's infrastructure labels May 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattbonnell mattbonnell

Labels
enhancement New feature or request infra Pertains to the app's infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mattbonnell