4 ms·
It strikes me that you could easily satisfy this by running a Redis process local to your application node as a cache and, indeed, you probably should instead o
by ixtli 7y ago
It strikes me that you could easily satisfy this by running a Redis process local to your application node as a cache and, indeed, you probably should instead of trying to re-implement functionality yourself.
Also redis is cool for pub/sub.
- hinkley 7y agoIf your rate of churn is low. It’s fairly easy to get a server with excess memory, especially if you’ve pushed state out of your services, such that having a kv sidecar isn’t that onerous. But then you get cache invalidation issues you have to find a solution for.