Redis 4.0
groups.google.com
Redis 4.0
1–10 of 184 posts
Re: Redis 4.0
#2LFU policy sounds really interesting!
Re: Redis 4.0
#3LFU policy sounds really interesting!
Thank you, there is more info in this blog post: http://antirez.com/news/109
Re: Redis 4.0
#4@antirez: Congrats! Are you going to modularize disque now that v4 is ready?
Re: Redis 4.0
#5I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.
Re: Redis 4.0
#6I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.
The words only have meaning if you give them meaning, and while a smaller progressive org might care, it doesn't seem to be a fight worth having. No one thinks your technical terminology supports the historical subjucation of a race, and I wish we could be adults and get on to real work.
Outrage fatigue is a thing. I just want to build, and save the politics for my off hours.
Edit: mods, feel free to detach as off topic. I did not expect this to go off the rails, and I don't want to take away from antirez's achievement
Re: Redis 4.0
#7@antirez: Congrats! Are you going to modularize disque now that v4 is ready?
Yes, one of the top items in the Redis 4.2 roadmap is to port Disque as a Redis module, so the steps are: 1) Implement a Redis Cluster modules API (I've already some draft design, basically there are low level stuff to enlist nodes, broadcast messages, send one-to-one messages, and have callbacks called when we receive a message), and then port Disque as Redis module on top of such API, so that we can both validate that the Cluster API is good enough with a real project, and can make Disque a first citizen of the Redis ecosystem without all the code duplication, that in the end, made the project extremely hard to sustain. Thanks.
Re: Redis 4.0
#8I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.
They have a note on it in the docs for SLAVEOF: https://redis.io/commands/slaveof
They stuck with it to avoid breaking backwards compatibility.
Re: Redis 4.0
#9I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.
I'm not for the change in terminology at this step, because it is very unfortunate to change the terminology of a project that is here for years, however I tried to use the fact we have this terminology to remind people of what slavery looked (and still looks in certain parts of the world) like, so:
1) We have a SLAVEOF NO ONE command which is very popular.
2) We have a note about slavery here: https://redis.io/commands/slaveof
For new projects I suggest to pick other terms as well, even because master and slave are kinda inelegant IMHO other than linked to bad things.
Re: Redis 4.0
#10I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.
This terminology has been used for a long time in computing. It's immediately recognised by everyone and in no way endorses human slavery. I'm getting quite fed up of the OTT political correctness movement in tech.
Out of interest, what is your opinion on male/female USB connectors? Does one deserve to get fired if they make a joke about "big dongles"?