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 I almost mentioned in #43, the caching mechanism we're using right now, always assumes in-memory usage.
This works very well as it is right now, but the way the code is structured could be better. If we reach for a more flat structure, it would be easier to expand/replace to another type of persistent storage later. Right now we're also pretty inefficient in the way we are storing data for the cache
As I almost mentioned in #43, the caching mechanism we're using right now, always assumes in-memory usage.
This works very well as it is right now, but the way the code is structured could be better. If we reach for a more flat structure, it would be easier to expand/replace to another type of persistent storage later. Right now we're also pretty inefficient in the way we are storing data for the cache
Here's an example entry:
The key is the value, just stringified, and without the id.
The text was updated successfully, but these errors were encountered: