Looking forward to Redis 2.6

In reading Short term Redis plans, I’m happy to see the “More introspection” section. For a long time some in the Redis community have asked for the ability to publish key names to a channel when they expire. And, while I sympathize with their desire for such a feature, I also realize that it’s not the greatest solution to the problem (since pub/sub is best effort–a client could be disconnected for a bit and miss messages).

But it looks like Salvatore is taking things a step or two farther…

There is a plan to use Pub/Sub in order to communicate events happening inside Redis, like a key that expired, clients connecting / disconnecting, operations performed against keys. We’ll probably allow the user to script this feature with Lua so that you can, for instance, push all the keys expired inside a list as well, or other things that can’t be reliably done with clients and Pub/Sub since the client is not guaranteed to get all the messages (it can get disconnected for some reason).

This strikes me as really good. He’s been listening to feature requests for a long time. Some appear and vanish after a short time, while others persist. This has been a persistent request for a long time now. Building it in a way that allows for robust notification ought to make everyone happy.

I’ve personally not allowed myself to design systems that would require knowing when a key expires, but seeing this on the roadmap really does open up a lot of possibilities for future work.

About Jeremy Zawodny

I'm a software engineer and pilot. I work at craigslist by day, hacking on various bits of back-end software and data systems. As a pilot, I fly a Flight Design CTSW and high performance gliders in the northern California and Nevada area. I'm also the original author of "High Performance MySQL" published by O'Reilly Media. I still speak at conferences and user groups on occasion.
This entry was posted in programming, redis, tech. Bookmark the permalink.

One Response to Looking forward to Redis 2.6

  1. Neil says:

    this is out of place, but I got here via your old blog post from 2005:

    I bet you didn’t know how easy it is to get your My Yahoo! subscriptions as an OPML file.

    If you’re a My Yahoo! user, point your browser to this URL:

    http://api2.my.yahoo.com/2.0/content/getsubs

    and you’ll be greeted by an OPML representation of your subscriptions.

    The catch is that you need to be already logged in–that is, you need a valid Yahoo! cookie for it to work. If you’re already using My Yahoo! regularly, that’s a non-issue. When a more web services friendly login/auth API appears someday, you’ll be able to automate the process to backup or sync your subs with a blogroll, etc.

    I am a user, not a programmer, fed up with my 11 year old Yahoo news reader. I want to move to Google but hope to not have to rebuild the page manually. Can you point me to some help?
    thanks, Neil

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s