In March, Redis announced that it was dumping the open source BSD 3-clause license for its Redis in-memory key-value database, instead adopting a “source-available” Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). That made both developers and users unhappy. So as open source people do, members of the community forked the code into Valkey with the support of The Linux Foundation. This move has proved much more popular than expected.
Madelyn Olson, an Amazon Web Services (AWS) software engineer and a Valkey maintainer, announced at the Open Source Summit in Seattle the availability of the first release, Valkey 7.2.5 GA. This release is based on the last open source version of Redis, 7.2.4. That’s good news, but it’s not big news. That’s what we expect from forks.
AWS, Ericsson, Google Cloud, Oracle and Verizon had all said they were supporting the fork. Now Alibaba Cloud, Aiven, Heroku and Percona are backing Valkey as well. I’ve seen many forks take off and overcome their parent projects – LibreOffice over OpenOffice comes to mind — but I’ve never seen one where so many Fortune 500 businesses spun on their heels to drop one project for another.
Olson said in her keynote speech, “These companies are planning to continue or even increase their contributions. Their support is needed for the long-term health and viability of the project. The community is thankful for their support, which will help keep the project open and keep our developers moving at the pace that our users demand.”
The Valkey fork’s maintainers have the technical chops needed to fulfill those business needs. As Olson pointed out, its technical leadership committee has 26 years of experience and over 1,000 commits to the open source project. Indeed, Tencent’s Binbin Zhu, a committee member, alone contributed almost a quarter of the open source Redis commits.
At the time of the fork, Redis CEO Rowan Trollope didn’t seem too worried. “The major cloud service providers have all benefited commercially from the Redis open source project, so it’s not surprising that they are launching a fork within a foundation,” he wrote. And he added, “Innovation has been and always will be the differentiating factor between the success of Redis and any alternative solution.”
With so many top maintainers now at Valkey, that assertion may be hard to pull off. As Heroku’s CTO Gail Frederick said during the conference, “With this group of experienced contributors and broad industry backing, Valkey is continuing the open source model that’s been transformative for developers everywhere.”
So many top Redis (the software) customers shifting to Valkey presents Redis (the company) with serious challenges. After all, Redis was the most popular database on AWS and by DB-Engine’s latest count, it’s the most popular key-value DBMS.
It appears that many of those customers are now on their way to Valkey.
Kyle Davis, an AWS senior developer advocate and former Redis employee, said, “AWS is committed to supporting open source Valkey for the long term. We are adding Valkey support to our ElastiCache and MemoryDB managed database services, which are built on open source Redis.”
Karan Singh, Oracle’s Director of Data and AI Product Management, wrote that “Oracle Cloud Infrastructure (OCI) Cache will continue supporting its current Redis 7.0-based service because the license changes don’t impact it.” However, Oracle is dropping the name Redis from its offering and is “working on integrating Valkey support into the OCI Cache service to ensure our unique in-memory database offerings on OCI continue to benefit from open source advancements, enhancing value for our customers.”
Empirical data suggests users are also moving away from Redis. Peter Zaitsev, Percona CEO, noted that DB-Engine is already showing a drop of interest in Redis.
Redis’s move attracted a lot of snarkiness. For example, Corey Quinn, chief cloud economist at The Duckbill Group, an AWS analyst firm, tweeted, “Good morning to everyone except the thieves at Redis. You didn’t build it; you stole it from the community. If you want it from the ones who built it, it’s called Valkey.”
What we’re seeing here is not open source fans copping an attitude. It’s companies and developers alike making a major move away from Redis.
Filed Under: Blogs, DevOps and Open Technologies, DevOps Practice, DevOps Toolbox, Features, News, Social – Facebook, Social – X Tagged With: database, dbms, key-value database, Linux Foundation, open source, Redis, source available, valkey
Secure Coding Practices
Step 1 of 7
14%
Does your organization currently implement secure guardrails in the software development process?(Required)
Yes, extensively across all projects
Yes, but only in specific projects or teams
In the process of implementation
No, but planning to in the near future
No, and no plans to implement
What are the biggest challenges you face in implementing secure guardrails within your development processes? (Select all that apply)(Required)
Lack of awareness or understanding
Technical difficulties in integration
Resistance from development teams
Lack of suitable tools
Cost constraints
Other
Other, tell us more:
How effective do you find secure guardrails in preventing security vulnerabilities in your projects? Rate on a scale from 1 (Not effective) to 5 (Highly effective)(Required)
1
2
3
4
5
To what extent are your secure guardrails automated?(Required)
Fully automated
Mostly automated with some manual processes
Equally automated and manual
Mostly manual with some automation
Entirely manual
What features do you prioritize in a secure guardrail solution? (Rank in order of importance)Ease of integration into existing workflowsComprehensive coverage of security vulnerabilitiesCustomizability for specific project needsMinimal impact on development speedActionable insights and recommendationsSupport for a wide range of programming languages and frameworks
What are your organization’s plans regarding the adoption or enhancement of secure guardrails within the next 12 months?(Required)
Expand the use of secure guardrails to more projects
Enhance the capabilities of existing secure guardrails
Maintain current level of secure guardrail use without changes
Reduce reliance on secure guardrails
No plans related to secure guardrails
What best describes your primary role?(Required)
Security Engineer
DevOps Engineer
Platform Engineer
Security champion on the development team
Software Developer
CISO (or equivalent)
Sr. Management (CEO, CTO, CIO, CPO, VP)
Manager, Director
Other
Δ
