Redis Users Want a Change
The key-value store landscape is experiencing a shake-up, as Redis’ recent licensing changes have driven users to search for alternatives. Our latest Percona survey looks deeper into this trend, highlighting the impact of Redis’ licensing changes on organizations and the growing interest in Valkey, a popular open source Redis fork.
Redis Licensing Changes: A Catalyst for Migration
Redis’ shift to the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1) earlier this year has caused organizations to rethink their database strategies. Concerned about potential increases in licensing costs and future open source bait-and-switch tactics, many in the IT community are seeking alternatives that offer similar functionality without the associated risks, costs and vendor lock-in.
The potential impact of this trend is huge.
While Redis remains the dominant key-value store in use, according to both DB Engines and the Percona survey, a striking 75% of surveyed Redis users are planning to seek an alternative.
What do you think about Redis moving the codebase to a more restrictive license?
Madelyn Olson, AWS engineer and Valkey project maintainer, said, “Percona’s survey helps underscore the importance of the Valkey project and illustrates the strength of our community-led initiative. This survey highlights the need for an open source fork of Redis and the strength and momentum we are gathering from companies of varying sizes and needs. As a core maintainer of the project, we see this as a sign of Valkey’s value as the open source alternative to Redis.”
Valkey: A Rising Star
Following Redis’s announcement, Valkey, an open source alternative to Redis, quickly emerged as a leading alternative. In fact, according to the Percona Survey, more than 63% of respondents were already familiar with Valkey — a remarkable level of awareness given that it had only been a few weeks since Valkey’s inception. And of that 63%, more than 75% are considering Valkey as an alternative to Redis’ functionality.
When asked to share their reasons behind seeking a Redis alternative, the respondents offered the following:
- Many respondents indicated that the open source, Linux Foundation-supported nature of Valkey played a significant role in their decision to consider it.
- Larger, more cautious organizations plan to test Valkey before making a possible switch.
- Long-term Redis users plan to evaluate Valkey but remain uncertain about the level of in-house expertise needed, as well as the availability of commercial support and managed services.
The respondents who plan to continue to use Redis shared the following reasons why:
- The widespread use of Redis and its dependencies in the infrastructure mean some enterprises will likely continue using Redis despite licensing changes. They may consider Valkey for future development projects.
- Their current Redis deployment is too large to migrate right now, but they plan to migrate to Valkey gradually.
- Some say Redis has been a reliable technology, and they see the value in paying for it. These responses mostly came from software developers, who have consistently named Redis one of their most loved databases in Stack Overflow Surveys year after year.
When filtering by company size, those from micro, small- and mid-size businesses stated they are more likely to migrate from Redis sooner than midmarket, large and enterprise organizations. The latter three are currently testing alternatives and evaluating their options before making a decision.
What do you think about Redis moving the codebase to a more restrictive license? (Responses segmented by company size)
Drilling one level down, large and enterprise organizations represent the biggest cohort that plans to migrate to Valkey. This is understandable, as the impact of licensing changes tends to be more substantial for organizations that handle large amounts of data. However, these organizations tend to migrate to alternatives more slowly due to potential downtime and operational support considerations.
Have you already decided to adopt Valkey in your organization? (Responses segmented by company size)
To accelerate adoption, the Valkey community and endorsers should consider providing the necessary tools and services to ensure a smooth transition to the Redis alternative.
Valkey Support Options Needed
Redis’ community support infrastructure allowed it to thrive as an open source project, attracting a diverse user base and fostering rapid growth. But for organizations that plan to use Redis alternatives in production, operational support considerations may impact the speed of adoption.
The survey reveals varied support strategies: Some organizations are unsure about internal support needs; some will wait for managed versions of Valkey and others will seek external support. Most organizations (75.5%) plan to use third-party enterprise support, while a minority (24.55%) plan to rely on in-house teams or community resources for Valkey maintenance.
Do you consider the availability of external vendor support for open source projects like Valkey an important factor when making technology decisions?
This is a pivotal moment in the evolution of the key-value store landscape, with Valkey poised to gain significant traction as organizations seek open source alternatives to Redis. As Valkey continues to evolve, its ability to meet organizations’ diverse needs, coupled with strong commercial backing, will be crucial in solidifying its position in the market.
For more on these trends, you can review the full survey.
