You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: