With AWS launching a bunch of cool stuff and now Redis 4 going into RC this week has felt like Christmas come early.
Antirez keeps adding features I didn't know I always needed (ok...wanted), while keeping the same performant core.
Redis 4.0 RC1 is out
11–20 of 30 posts
Re: Redis 4.0 RC1 is out
#12The new LRU algorithm (which he calls Last Frequently Used) is in this release. I really enjoyed the blog post on it when it was developed [0]. Very cool to see a real-word pragmatic solutions to this common/hard problem developed in the open (and in a very readable code-base). I've read through it thinking about my own LRU use in my own applications! There are only two hard things in Computer Science: cache invalida…
There are only two hard things in Computer Science: cache invalidation, naming things, and off by one.
Re: Redis 4.0 RC1 is out
#13The new LRU algorithm (which he calls Last Frequently Used) is in this release. I really enjoyed the blog post on it when it was developed [0]. Very cool to see a real-word pragmatic solutions to this common/hard problem developed in the open (and in a very readable code-base). I've read through it thinking about my own LRU use in my own applications! There are only two hard things in Computer Science: cache invalida…
There are only two hard things in Computer Science: cache invalidation, naming things, and off by one.
Haha that last one's been nagging me lately every time the kids ask how many days are left till Christmas.
Re: Redis 4.0 RC1 is out
#14> There are reasons why UNLINK is not the default for DEL. I know things… I can’t talk. Doesn't inspire confidence
Ok I'll talk ;-) The matter is that currently, if you delete a key, you know that the command returns once the memory is reclaimed. UNLINK is conceptually like DEL, but the memory reclaiming, while fast because there is a thread doing only like that, is asynchronous. So in certain use cases, while semantically identical if you think at what happens to data, the two commands are semantically different in the way memor…
Maybe a new command like "DELSYNC" should be added that acts like the current DEL behavior, and in a future version DEL could be changed to act like UNLINK?
Re: Redis 4.0 RC1 is out
#15> There are reasons why UNLINK is not the default for DEL. I know things… I can’t talk. Doesn't inspire confidence
Ok I'll talk ;-) The matter is that currently, if you delete a key, you know that the command returns once the memory is reclaimed. UNLINK is conceptually like DEL, but the memory reclaiming, while fast because there is a thread doing only like that, is asynchronous. So in certain use cases, while semantically identical if you think at what happens to data, the two commands are semantically different in the way memor…
This doesn't sound so bad. Should just state this limitation clearly in the notes.
Otherwise people will assume something a lot worse is going on given how you phrased it.
Re: Redis 4.0 RC1 is out
#16Earlier quoted context omitted.
Ok I'll talk ;-) The matter is that currently, if you delete a key, you know that the command returns once the memory is reclaimed. UNLINK is conceptually like DEL, but the memory reclaiming, while fast because there is a thread doing only like that, is asynchronous. So in certain use cases, while semantically identical if you think at what happens to data, the two commands are semantically different in the way memor…
This doesn't sound so bad. Should just state this limitation clearly in the notes. Otherwise people will assume something a lot worse is going on given how you phrased it.
Yep it was just a joke. I'll update the post.
Re: Redis 4.0 RC1 is out
#17Re: Redis 4.0 RC1 is out
#18Any links to the timeseries modules mentioned in the post? Have found some npm modules that wrap timeseries around the API, I think, but not any modules that are directly integrating with Redis.
Re: Redis 4.0 RC1 is out
#19Any links to the timeseries modules mentioned in the post? Have found some npm modules that wrap timeseries around the API, I think, but not any modules that are directly integrating with Redis.
Re: Redis 4.0 RC1 is out
#20Personally, modules have been the thing I wanted most in redis for years, and it's been a delightful experience working on modules for the past months. I really think it's a game changer for redis and I can't wait to see where this will take it in the coming years.
Some modules that are already out there (full disclosure - I work at Redis Labs and I've developed a couple of those):
* redis-cell - a rate limiter module https://github.com/brandur/redis-cell
* Redis Graph - a graph DB with a subset of Cipher for querying. https://github.com/swilly22/redis-module-graph
* RediSeach - fast full-text search engine with fuzzy auto-suggest. https://github.com/RedisLabsModules/RediSearch
* redis-ml: Machine learning models as redis data types. https://github.com/RedisLabsModules/redis-ml
* redablooms - scalable bloom filters https://github.com/RedisLabsModules/redablooms
* Secondary indexes with a small subset of SQL for WHERE clauses. https://github.com/RedisLabsModules/secondary
* Time Series https://github.com/saginoam/RedisModuleTimeSeries
PS If you're interested in creating modules, we've started a community for module developers. https://groups.google.com/forum/#!forum/redis-module-devs