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

Problematic usage of the EntityLookupCache in app runner #107

Open
leoschwarz opened this issue Nov 22, 2024 · 0 comments
Open

Problematic usage of the EntityLookupCache in app runner #107

leoschwarz opened this issue Nov 22, 2024 · 0 comments
Assignees

Comments

@leoschwarz
Copy link
Collaborator

The concept of caching there should be revisited. The problem is that entities remain cached after being updated. Fixing this properly would be too much implementation effort as it would require creating a full ORM.

My new favorite for the caching api is the follows:

  • Cache by default caches no entities.
  • Each entity type can be registered to be cached. Two options are possible:
    • In memory
    • In file
  • This configuration is available as a pydantic model and can be configured from yaml.
  • Unclear: Retention time to be defined
@leoschwarz leoschwarz self-assigned this Nov 22, 2024
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