Rethinking the Redis EXPIRE command

This article discusses several changes we have made to the EXPIRE command and how it works. We have added the ability to expire individual members of a set with the EXPIREMEMBER command and have also enabled active deletion to operate in near real time which has big advantages for those who rely heavily on using expires in production. Throughout the work with the EXPIRE command we have actually achieved 5-10% memory savings with these.

Running KeyDB on Arm-based Amazon EC2 A1 Instances for the Best Price/Performance

We’ve talked to many of our users who were looking to optimize their cost on AWS. While most had experimented with the many available x86 based instance types we were surprised that few had tried the Arm-based Amazon EC2 A1 instances. These Arm-based instances come with unique performance advantages for multi-threaded cache server workloads. To understand why cache databases, and KeyDB specifically, is uniquely suited to Arm we have to first understand a little about the hardware.

Redis Replication and KeyDB Active Replication: Optimizing System Resources

A lot of sites run replica nodes for high availability of their servers. Makes sense, but is this replica being fully utilized? Or are you just paying for high availability without getting the performance boost of essentially doubling your resources? This article discusses options used with Redis, as well as the active-replication option used in the Redis compatible database KeyDB.

How Fast can A Single Instance of Redis be?

Redis is known as one of the fastest databases out there. But what if some of the limitations were removed, how fast could a stand-alone instance become? We often hear that Redis will likely become network bound or memory bound before it is CPU bound on performance limitations. Depending on your setup it could be any of these.

In this article we are going to discuss how we made a module that nearly doubles Redis performance!

A Brief History of Existential Threats to Open Source

How times have changed. In the early 2000s Steve Ballmer famously called Linux a “cancer”. But Microsoft was not the biggest threat. A debate was raging that threatened to sow confusion, fracture the community, and derail open source as a whole. Should people who modify open source software be required to open source their changes as the GPL requires? Or should they be free to do as they wished even if that meant keeping their changes proprietary? The fight was over developer freedom vs user freedom, with the Free Software Foundation in one ring, and Apache Software Foundation in the other. Without a united front open source was doomed — or so Microsoft hoped.