December 31st, 2015 – Edition #60

A Newsletter About Everything Redis

EOY Edition #60
December 31st, 2015

# include i.h

1451606400 is almost here! Two extra bits that caught my attention underflowed to this section:

Happy 0b11111100000!

Redis Trivia: 6379 is 0b1100011101011

Be social, tweet about the last edition of Redis Watch for 2015: I'm reading Redis Watch #60:

Virtual Moka Pot

Since time immemorial within the Redis community, a Moka Pot is considered a token of appreciation to a member for her/his contributions. Iā€™d like to present this one to RB_GC_GUARD(v) “Jan-Erik Rediger” @badboy_ for his years-long activity and countless contributions to the Redis community. Just to give a taste, here are a few recent ones:

Jan-Erik – for being the total opposite of your handle, may your coffee always taste as good as a cup of Italian Moka, danke und ein glückliches neues Jahr.

int main(int argc, char **argv) { 

Redis 3.2 Release Candidate 1 is out! (4 minutes to read)

It could be because Redis’ development is moving towards a time-driven release cycle, but the latest release from Salvatore Sanfilippo @antirez feels like an Xmas gift to me – it is filled to the brim with goodness that we’ve been waiting for forever. The new functionality includes geospatial indexes, cluster rebalancing, Lua effects replication, an embedded Lua debugger and variadic SPOP (!!!). And while all this will certainly delight developer personas, the new version has more than enough for the operations-minded folks as well as it brings drastic improvements in performance and memory overheads of many use cases.

Because most changes have been thoroughly tested prior to the release candidate’s release, v3.2RC1 is likely to be around only for a short while. Another release candidate for the cluster’s integration with Docker and security improvements will replace it, so in all likelihood v3.2 will be production-ready early next year.

Redis 3.0.6 and 2.8.24 are out (2 minutes to read)

A minor release that includes a few fixes and backports from v3.2. Most notably, a rare crash was addressed and an integer overflow security vulnerability in Lua was fixed. The recommended upgrade urgency is MODERATE.

3 Critical Points about Security (3.14 minutes to read, an eternity in hell if you don’t) #PSA

  1. Never leave an unprotected server open to the outside world
  2. If your server has been compromised – burn it
  3. Always read the documentation

Memory As A Service (2 minutes to read) #MaaS

I admire the work that John Matherly @achillean is doing to raise public awareness to security issues, and at least some of the recent NoSQL-security-related public debates can be attributed directly to him and the Shodan @shodanhq project. When you think about it, the only way to address security vulnerabilities is to publicly expose them since otherwise they remain exposed to potential wrongdoers. While this post is about #Memcached, the lessons apply to most databases that are publicly exposed, Redis included. This post also deserves a <3 for the creative term-coining in title.

swizzlr/swift-redis #Swift #foss

Apparently, Apple’s Swift has just become a serious server-side language šŸ™‚ by Swizzmas @swizzlr.

OH Sam Saffron @samsaffron > @dhh this is just a bit too much…#L28 now every Rails install requires redis, eventmacine, celluloid and faye <- Do Action Cable’s dependencies derail #Rails5?

Redis For Everything (25:59 minutes to watch)

Yaron Wittenstein @RealWittenstein from Spot.IM @spot_im gave this delightful talk at the recent R@RailsIsrael (the view from a front-row seat) – via @Code4WD/Raphael Fogel @fogelmania.

Intro to Redis part 1 (5 minutes to read)

Even if only for its opening: “I’ve recently rekindled my love for Redis…its elegance lures me for every project.” – by “code warrior”_ Zack Urben @zackurben from @form_io. I hate #cliffhangers.

Under the Hood of Redis: Strings (Reading time ~11 minutes ) #InfernalInternals

For those of us who don’t read Russian, Nikolay Bondarenko @misterionkell put up a new promising blog and the first post is a great hard core #codeporn (albeit slightly outdated ;)) dive into Redis’ internals and the magical number 56.

OR @thoughtbot “Our most frequently used NoSQL database is Redis, which we use for storing transient, high quantity read/write data” (source:


Redis Labs

Redis Labs is HIRING!!!

Check out our many careers enabling the full power of Redis to the enterprises!

Happy holidays and new year

Questions? Feedback? Anything you want to share? Email or tweet me – I'm highly available šŸ™‚


This newsletter was produced and distributed by Redis Labs, Inc.

Redis Labs, Inc. 700E El Camino Real, Suite 170, Mountain View, CA 94041

Repository |Archive | Subscribe | Follow on Twitter