https://antirez.com/rss

Today it happened again.

Human beings have a strong tendency to put new facts into pre-existing categories.

Today a page about the new Common Clause license in the Redis Labs web site was interpreted as if Redis itself switched license.

A bit more than one month ago I received an email from the Apple Information Security team.

A few days ago I started my day with my Twitter feed full of articles saying something like: “75% of Redis servers infected by malware”.

[This blog post is also experimentally available on Medium: https://medium.com/antirez/a-short-tale-of-a-read-overflow-b9210d339cff] When a long running process crashes, it is pretty uncool.

I saw multiple users asking me what is happening with Streams, when they’ll be ready for production uses, and in general what’s the ETA and the plan of the feature.

Four days ago a user posted a critical issue in the Redis Github repository.

Until a few months ago, for me streams were no more than an interesting and relatively straightforward concept in the context of messaging.

Today I read an interesting article about how the Wolfenstein 3D game implemented a fade effect using a Linear Feedback Shift Register.

A 10x programmer is, in the mythology of programming, a programmer that can do ten times the work of another normal programmer, where for normal programmer we can imagine one good at doing its work, but without the magical abilities of the 10x programmer.

After 10 million of units sold, and practically an endless set of different applications and auxiliary devices, like sensors and displays, I think it’s deserved to say that the Raspberry Pi is not just a success, it also became one of the preferred platfo…

It’s not yet stable but it’s soon to become, and comes with a long list of things that will make Redis more useful for we users: finally Redis 4.0 Release Candidate 1 is here, and is bold enough to call itself 4.0 instead of 3.4.

Redis is often used for caching, in a setup where a fixed maximum memory to use is specified.

WARNING: Long pretty useless blog post.

I’m spending days trying to get a couple of APIs right.

It was a matter of time but it eventually happened.

I’m aboard of a flight bringing me to San Francisco.

It took more than expected, but finally we have it, Redis 3.2.0 stable is out with changes that may be useful to a big number of Redis users.

Today Redis is 7 years old, so to commemorate the event a bit I passed the latest couple of days doing a fun coding marathon to implement a new crazy command called BITFIELD.

Yesterday night I was re-reading Redlock analysis Martin Kleppmann wrote (http://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html).

Martin Kleppmann, a distributed systems researcher, yesterday published an analysis of Redlock (http://redis.io/topics/distlock), that you can find here: http://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html Redlock is a client side di…

Today I’m happy to announce that the first release candidate for Disque 1.0 is available.

Two days ago Mike Malone published an interesting post on Medium about the V8 implementation of Math.random(), and how weak is the quality of the PRNG used: http://bit.ly/1SPDraN.

Today I was curious about plotting all the Redis commits we have on Git, which are 90% of all the Redis commits.

Lua scripting is probably the most successful Redis feature, among the ones introduced when Redis was already pretty popular: no surprise that a few of the things users really want are about scripting.

IMPORTANT EDIT: Redis 3.2 security improved by implementing protected mode.

I’m just back from the Redis Dev meeting 2015.

If you know me, you know I’m not the kind of guy that considers competing products a bad thing.

Everybody knows Redis is single threaded.

Yesterday Amplitude published an article about scaling analytics, in the context of using the Set data type.

I consider myself very lucky for contributing to the open source.

Nor subjects, for what matters.

I’m back from Paris, DotScale 2015 was a very interesting conference.

EDIT: In case you missed it, Disque source code is now available at http://github.com/antirez/disque It is a few months that I spend ~ 15-20% of my time, mostly hours stolen to nights and weekends, working to a new system.

I’m back home, after a non easy trip, since to travel from San Francisco to Sicily is kinda NP complete: there are no solutions involving less than three flights.

Today Redis is six years old.

Redis speed could be one selling point for new users, so following the trend of comparative “advertising” it should be logical to have a few comparisons at Redis.io.

Today I was testing Redis latency using m3.medium EC2 instances.

One interesting thing about the Stripe blog post about Redis is that they included latency graphs obtained during their tests.

Yesterday Stripe engineers wrote a detailed report of why they had an issue with Redis.

Almost a month ago a number of people interested in Redis development met in London for the first Redis developers meeting.

Yesterday distributed systems expert Aphyr, posted a tweet about a Redis Sentinel issue experienced by an unknown company (that wishes to remain anonymous): “OH on Redis Sentinel "They kill -9'd the master, which caused a split brain..."

The first commit I can find in my git history about Redis Cluster is dated March 29 2011, but it is a “copy and commit” merge: the history of the cluster branch was destroyed since it was a total mess of work-in-progress commits, just to shape the initial…

Queues are an incredibly useful tool in modern computing, they are often used in order to perform some possibly slow computation at a latter time in web applications.

----------------- UPDATE: The algorithm is now described in the Redis documentation here => http://redis.io/topics/distlock.

The strong reactions about the recent OpenSSL bug are understandable: it is not fun when suddenly all the internet needs to be patched.

Generally speaking, I love randomized algorithms, but there is one I love particularly since even after you understand how it works, it still remains magical from a programmer point of view.

Yesterday and today I managed to spend some time with linenoise (http://github.com/antirez/linenoise), a minimal line-editing library designed to be a simple and small replacement for readline.

The title of this blog post is an apparently trivial to answer question, however it is worth to consider a bit better what performance really means: it is easy to get confused between scalability and performance, and to decompose performance, in the speci…