int main(int argc, char **argv) {
A CRITICAL update which temporarily reverts the recent upgrade the jemalloc’s v4 due to a potential deadlock issue.
Trivia bit: this is the first release ever to be published from Tel Aviv 🙂
Redis continues to be my favorite piece of software. Years and years of hammering and pushing on it, always impressed. Thank you @antirez.
Once v4.0 is released, here’s what Salvatore Sanfilippo @antirez has planned next. The gist of things: better cluster, better modules API and a Disque-as-a-module implementation (!), a Stream data structure and a complete overhaul – the Listpack – of the internal ziplist data structure.
Having a good time here in Tel Aviv with the Redis folks, many interesting discussions about Redis 4.2 and other stuff.
“Better Multi-DC story” – AMERICA needs only one DC, that’s the story. Shame! #draintheswamp.
Last month, Redis geeks and geekettes got the perfect Valentine’s gift: a day packed with sessions about everyone’s favorite in-memory database. The event turned out to be a huge success with over 200 attendees showing up and staying all the way until SHUTDOWN
. You can find photos from the day in the Twitter moment and in this folder.
One of the nicest things about Redis is that you find it practically everywhere (not unlike Chuck Norris). Another things you find everywhere are the internets, hence the IoT. Marrying the two makes a lot of sense (even if I don’t), so now (as in 4.0) not only can you run Redis on some of these critters, you can actually wring out impressive performance. A little further down along the road, “this will be even more interesting when the stream data structure will be available in Redis 4.2.”
As if to complement the above (but I know for a fact that this has been in the making before), Kyle @stockholmux implemented a Redis client on the ESP8266 Microcontroller for the sole and sacred purpose of keeping his wine properly chilled. Cool 🙂
redis is like the pair of front cutting pliers in my toolbox, surprisingly frequently used … more so than my hammer or screwdrivers even
If Redis was a machete, I’d be Jason Voorhees
The development of this invaluable utility has been all but abandoned until recently. While plans are to have this sort of functionality wrapped into Redis proper in all eventuality, we can until then resort to the updated package that includes:
This one is gonna be a hit: a time series database that already integrates with StatsD and Grafana. By friend and colleague Spaghetti Monster @dannidevmo.
Here’s an overview and demonstration from Denis Rystsov @rystsov, author of yesteredition’s GryadkaJS, about how Single Decree Paxos is simpler than Multi-Paxos and Raft.
You come to me
in your time of need
with redis code
checking keys for change
and #FIXME: race condition
and yet
you have not used locks
Any self-respecting nerd knows there’s nothing is more exciting than a peek under the hood. This golden nugget from James Fisher @MrJamesFisher of Pusher @pusher (congrats for the inaugural post, looking forward to its next parts!) is sure to scratch that itch, with a delightfully detailed deep dive into Redis’ Pub/Sub internals.
If you ever needed a tutorial on how to get your Redis mojo going on Google Cloud @googlecloud, this one by Jason Follas @jfollas should get you sorted. Via Falafel Software Inc @falafelsoftware.
Carlos Justiniano @cjus teaches by example, showing microservices are put together to create a game with distributed messaging. To do that he’s using Hydra, a NodeJS light-weight library for building distributed computing applications, and the Super Glue of Microservices: Redis. Via RisingStack @RisingStack.
A light introduction to Sorted Sets and some of their uses from Lorna Mitchell @lornajane, who own admission:
I work with a bunch of datastores and I probably shouldn’t have favourites – but if I did, Redis would be one of them!”
The need to scale is a mixed blessing – on the one hand you’re doing so good that you’re growing, but on the other hand supporting that growth means more work. The database tier is traditionally an especially hairy scaling challenge, and one way to tackle it is to think outside the box – instead of making your database faster/bigger/better, offload some of the work to a nimbler solution. Which is exactly what Derrick Reimer @derrickreimer of Drip @getdrip did by live caching his Postgres database:
The sorted and unsorted set data types are the killer features that made us choose Redis
To offset the previous item, here’s one from Brad Culberson @bculberson who wisely advocates restraint before rushing to caching. Put differently, don’t sell the plow to buy the mule.
Should be very useful – provides connection pooling and auto-reconnect for classic hiredis client.
Neato – implement an activity feed in 15 minutes or less by Konstantin (kig) @kig.
This is nice, despite the WWII imagery – the recounting of a first impression from a Redis n00b. Via BuiltinPerl @BuiltinPerl.
Seems to get a lot of hate, but systemd has totally made my life easier. It’s not Redis good, but it’s still good software 🙂
That’s a good one.
Here is what appears to be a hack-tension for making Redis OSS cluster work with password authentication. Try at your own risk.
For developers on Windows who want a local taste of the real thing. By Jingya Wang @JWT0T.
@antirez What comes to mind when I’m working with Redis. Thank you so much for such a great tool.
Ohm.
I’m so pissed that everyone sold Redis et al. as “no SQL” and not “fucking awesome completely different way of thinking about persistence”
Word.