 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
We’ve got to stop meeting like this, Linux Foundation.
Thursday, the foundation announced that intends to back a fork of the formerly open source Redis in-memory data store, swiftly following the news that Redis itself moved the code base to a more restrictive license.
Beginning with version 7.4. Redis will be dual-licensed under the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). Older versions will remain open source.
As a result, the Linux Foundation is putting its weight behind a new project named Valkey, as “an open source alternative to the Redis in-memory, NoSQL data store.
Already, a number of industry players have quickly joined in, including Amazon Web Services (AWS), Google Cloud, and Oracle.
“By forming Valkey, contributors can pick up where we left off and continue to contribute to a vibrant open source community,” said Madelyn Olson, an AWS principal engineer and former longtime Redis maintainer who co-launched Valkey, in a statement.
“It is nice to see a strong community forming so quickly around Valkey,” chimed in Andi Gutmans, Google Cloud GM and VP of Engineering for Databases, also in a statement.
At launch, the project has nine contributors — including Olson and two other AWS engineers — and has garnered 1,500 GitHub stars.
Valkey will use Redis v. 7.2.4 as the base, placing it under the open source Berkeley Software Distribution (BSD) three-clause license.
In an e-mail response to The New Stack, Redis CEO Rowan Trollope all but scoffed at the fork, casting it as the underhanded work of stingy cloud providers to get out of paying licensing fees.
“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,” Trollope wrote.
Redis’ licensing change was a move to establish fair licensing agreements with the cloud providers, Trollope explained. Microsoft came to an agreement, while AWS and GCP have yet to strike a bargain.
Like HashiCorp did before, Redis stressed its commitment to enterprise excellence.
“We remain focused on our role as stewards of the Redis project, and our mission of investing in the Redis source available product, the ecosystem, the developer experience, and serving our customers,” Trollope wrote. “Innovation has been and always will be the differentiating factor between the success of Redis and any alternative solution.”
Naturally, industry observers remain skeptical.
This is the “worst outcome” for Redis labs, wrote System Initiative Co-founder Adam Jacob on X.
“Congratulations! You now have a competitor that’s well funded, ships a trustable product at $0, and will obviously be what cloud providers use to compete,” he tweeted.
In open source terms, forking is the process of copying a code base and then developing it independently of the originator, often resulting in two separate and soon incompatible code bases.
This is the second time that the non-profit Linux Foundation has backed forkings of commercial software after its (commercially-minded) creator pulled back the licensing terms. In September the foundation cloned Terraform just a month after HashiCorp moved that Infrastructure as Code (IaC) software to a non-open source, view-only BSL (Business Source License). The software was renamed OpenTofu.
The HashiCorp Vault secrets manager was also forked, by engineers at IBM, into OpenBao, with the aim of becoming a Linux Foundation Edge project.
Following an industry trend, both Redis and HashiCorp have expressed business reasons for moving their respective code bases out of open source licensing, joining other companies in the practice such as Elastic and MongoDB.
In its most recent survey, DB_Engines ranks Redis as the sixth most widely-used database worldwide.
The Redis project was created in 2009 by Salvatore Sanfilippo as a high-performance key/value store that can be used for caching or as a speedy data store for real-time data analysis, session store, message broker, and many other use cases. Thousands of developers have contributed to the project.
Initially, Valkey (an inverse abbreviation of “key-value”) will run on the Linux, macOS, OpenBSD, NetBSD, and FreeBSD platforms.
The development team plans to continue on the existing Redis roadmap, with planned improvements in slot migration, scalability and stability to the clustering system. Multithreaded performance improvements, triggers, new commands, and vector search support are also on the books.
“Fostering open collaboration that benefits all and not just a single organization is critical in building long-term, sustainable open source communities,” said Chris Aniszczyk, CTO of The Linux Foundation, in a statement. “Having this project in the hands of a foundation, rather than a single company, means Valkey will be community-driven without surprise license changes that break trust and disrupt a level open source playing field.”
A number of open source distributions, such as Red Hat‘s Fedora, currently include Redis in their packages, and would probably be hard-pressed to continue to do so given the more restrictive nature of the new Redis license.
The Foundation is not the only one looking to keep the Redis open source alive. The Redict project was also recently launched with this aim in mind.
David Cassel contributed to this post.
3/28: This post has been updated with input from Redis.
