5 ms·
Since I switched to Redis, I had massive drop in resource requirements, saving me a lot of money. Thank you very much. The keyspace notifications are great but
by miscoowow 13y ago
Since I switched to Redis, I had massive drop in resource requirements, saving me a lot of money. Thank you very much.
The keyspace notifications are great but I use NodeJS at the moment to listen to the events. When will it be possible to run Lua to remove the current point of failure? On the topics page, it says "In the future". Are we looking at years or months?
- antirez 13y agoAwesome that you improved your stack with Redis, thanks for sharing. I'm not sure about what exact feature you are referring to, please could you describe it? Thanks.
- miscoowow 13y agohttp://redis.io/topics/notifications http://redis.io/topics/notifications notify-keyspace-events Kx Currently, NodeJS subscribes to expired keys. When the key is expired it will delete the 'physical' data from the server (thumbnails, more indepth info, etc). If NodeJS fails, even for a few seconds, I will forever have the 'physical' data stored on the server (as it doesn't re-run the expired event). Having lua scripting do what NodeJS currently does would fix the problem. Apart from that, Redis is perfect. ;)
- seiji 13y agoI experimented with adding exactly that recently: https://matt.sh/advanced-redis-pubsub-scripts https://matt.sh/advanced-redis-pubsub-scripts (code in the branch at https://github.com/mattsta/redis/tree/pubsub-scripting https://github.com/mattsta/redis/tree/pubsub-scripting). It hasn't been extensively tested, but it works for my isolated test cases.