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

Caching credentials and data #41

Open
jchadwick opened this issue Dec 13, 2023 · 1 comment
Open

Caching credentials and data #41

jchadwick opened this issue Dec 13, 2023 · 1 comment

Comments

@jchadwick
Copy link
Contributor

jchadwick commented Dec 13, 2023

As it stands (at least from what I can tell), user credentials are stored on disk and data is stored in memory.

Neither of these things work well in a stateless, multi-user server-side scenario. Would be nice to have a cache implementation.

In my project I used keyv as the direct dependency/interface which allows you to use a variety of backends, including in-memory, file-based, and (of course) distributed caches. It also allows you to use TTLs to manage the data more effectively. If you like the idea, I can make a PR.

@codetheweb
Copy link
Owner

keyv works for me. Alternatively just allowing any object implementing get() / set() could work too.

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

2 participants