-
Notifications
You must be signed in to change notification settings - Fork 7
Optionally Cache DB Entities #761
Copy link
Copy link
Open
Labels
P3Low priority. No set deadline to address.Low priority. No set deadline to address.Size: LargeThe work involved in addressing this issue is substantial. Multiple days or weeks of work.The work involved in addressing this issue is substantial. Multiple days or weeks of work.Status: AvailableWork on this issue has not yet started and is available to be worked on.Work on this issue has not yet started and is available to be worked on.Type: FeatureAddresses adding a new feature to the application.Addresses adding a new feature to the application.
Milestone
Metadata
Metadata
Assignees
Labels
P3Low priority. No set deadline to address.Low priority. No set deadline to address.Size: LargeThe work involved in addressing this issue is substantial. Multiple days or weeks of work.The work involved in addressing this issue is substantial. Multiple days or weeks of work.Status: AvailableWork on this issue has not yet started and is available to be worked on.Work on this issue has not yet started and is available to be worked on.Type: FeatureAddresses adding a new feature to the application.Addresses adding a new feature to the application.
Describe the problem that this feature would solve
As a potential enhancement, we can add an option of a cache. Thunder will cache user entities that it fetches from the DB so that for frequently accessed users we don't have to go to the database.
Problems to consider:
Describe the solution you'd like
Additional context
https://github.com/google/guava/wiki/CachesExplained