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
When express receives a cache-able route (framedata, metadata, characterdata), call redis first with the url as the list and the version as the key within that list.
Redis should return the cached json blob in one response. If the json blob doesn't exist, it should call our controller to generate the response via mysql, pass it through, and then store it in redis.
This is super, super simple and stupid caching, but should give us alot of speed and efficiency games for very little work.
Mysql calls are synchronous, slow, and expensive. Since our app is just serving a big bundle of json data, I propose the following:
This is super, super simple and stupid caching, but should give us alot of speed and efficiency games for very little work.
I suspect we could use express middleware for this if we wanted: https://www.npmjs.com/package/express-redis-cache
The text was updated successfully, but these errors were encountered: