{"id":167143,"date":"2025-05-02T11:41:03","date_gmt":"2025-05-02T11:41:03","guid":{"rendered":"https:\/\/linuxiac.com\/?p=167143"},"modified":"2025-05-02T14:18:07","modified_gmt":"2025-05-02T14:18:07","slug":"welcome-back-to-the-open-source-family-redis","status":"publish","type":"post","link":"https:\/\/linuxiac.com\/welcome-back-to-the-open-source-family-redis\/","title":{"rendered":"Welcome Back to the Open-Source Family, Redis"},"content":{"rendered":"\n<p>Long story short: <a href=\"https:\/\/redis.io\/\" target=\"_blank\" rel=\"noreferrer noopener\">Redis<\/a> hit the scene in 2009 as an open-source project offering a free, in-memory key-value data store. It was so well-designed that over the next 15 years, it became the go-to solution for just about any software that needs that kind of functionality.<\/p>\n\n\n\n<p>That brings us to 2024, when a single decision sent shockwaves through the open-source community. <a href=\"https:\/\/linuxiac.com\/redis-is-no-more-open-source-software\/\">Redis chose to change its licensing model<\/a>, switching to <a href=\"https:\/\/redis.io\/blog\/redis-adopts-dual-source-available-licensing\/\" target=\"_blank\" rel=\"noreferrer noopener\">RSALv2 and SSPLv1<\/a>. The goal was to prevent large cloud providers such as AWS, Azure, GCP, and others from offering Redis as a service without contributing to its development.<\/p>\n\n\n\n<p>However, as you can expect, this move effectively meant Redis could no longer be considered truly open source.<\/p>\n\n\n\n<p>The response was lightning-fast. <a href=\"https:\/\/linuxiac.com\/valkey-a-new-redis-alternative\/\">Big tech companies<\/a>, including Amazon, Google, and Oracle, forked Redis to create <a href=\"https:\/\/valkey.io\/\" target=\"_blank\" rel=\"noreferrer noopener\">Valkey<\/a>, an open-source alternative licensed under the BSD license, to maintain the original open-source ethos and ensure continued community-driven development.<\/p>\n\n\n\n<p>What Redis might not have anticipated is that this move would also lead Linux distributions <a href=\"https:\/\/linuxiac.com\/arch-says-goodbye-to-redis-adopts-valkey\/\" target=\"_blank\">to remove Redis from their repositories<\/a>. In its place, they&#8217;re offering the new alternative\u2014Valkey\u2014which, backed by some of the biggest names in tech, has not only lived up to expectations but even surpassed Redis in some areas.<\/p>\n\n\n\n<p>In the end, it all comes down to visibility. When you lose that valuable free exposure\u2014millions of developers discovering your software just because it\u2019s the default option in various Linux distro repositories\u2014it changes the game a bit.<\/p>\n\n\n\n<p>That brings us to yesterday, when news surprised everyone\u2014but in the best way possible: <strong>Redis announced it\u2019s going back to open source.<\/strong> As of May 1, 2025, the project is available under the GNU Affero General Public License v3 (<a href=\"https:\/\/www.fsf.org\/bulletin\/2021\/fall\/the-fundamentals-of-the-agplv3\" target=\"_blank\" rel=\"noreferrer noopener\">AGPLv3<\/a>), a free, copyleft license based on the GNU GPL version 3 and the Affero General Public License.<\/p>\n\n\n\n<p>This results&nbsp;in a <a href=\"https:\/\/github.com\/redis\/redis?tab=License-1-ov-file#readme\" target=\"_blank\" rel=\"noopener\">tri-licensing model<\/a>: Redis 8 (<a href=\"https:\/\/linuxiac.com\/redis-8-the-fastest-and-most-versatile-redis-yet\/\" target=\"_blank\">already available<\/a>) ships under AGPLv3, while the previous RSALv2 and SSPLv1 options remain for those who prefer them. It&#8217;s worth noting that this release comes with some really great new options:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Vector Sets.<\/strong> The first brand-new data type in years lets developers store and query high-dimensional embeddings natively, turning Redis into a lightweight vector database for retrieval-augmented generation (RAG) workloads.<\/li>\n\n\n\n<li><strong>Stack modules are now built-in.<\/strong> JSON, TimeSeries, probabilistic structures (Bloom, Cuckoo, Count-Min, Top-K), and the Redis Query Engine have moved from the separate Redis Stack distribution into core Redis, eliminating the two-track maintenance headache that previously slowed innovation.<\/li>\n\n\n\n<li><strong>Speed, speed, speed.<\/strong> More than 30 performance patches deliver up to 87 percent faster common commands, 2\u00d7 higher operations per second, 18 percent faster replication, and as much as 16\u00d7 query acceleration when the new Query Engine is in play.<\/li>\n<\/ul>\n\n\n\n<p>What next? First, under AGPL, any provider offering Redis 8 \u201cas a service\u201d must publicly release its source code changes. At the same time, I don\u2019t think big cloud providers (Google, Amazon, Microsoft) will drop their Valkey offerings just because they can use Redis again. They&#8217;ve already invested a lot into Valkey, which has proven itself as a solid enterprise solution.<\/p>\n\n\n\n<p>Will Redis make its way back into Linux distribution repositories? Most likely, yes. But this time, it\u2019ll share the stage with Valkey, which benefits all developers. Competition is a good thing.<\/p>\n\n\n\n<p>One thing\u2019s for sure\u2014Redis coming back to the open source world is a great move, and it\u2019s one that deserves a warm welcome. But there\u2019s still an important point to consider when it comes to the community, which has always been especially sensitive to decisions like the one Redis made in March 2024. That point is trust.<\/p>\n\n\n\n<p>Let\u2019s be honest\u2014moves like that can shake it. And like it or not, open source folks have long memories. Plenty of examples of projects made similar pivots and then struggled to regain their former credibility and community support.<\/p>\n\n\n\n<p>But with Redis, I truly hope that won\u2019t be the case. It\u2019s a fantastic piece of software and deserves a strong, open future. So, all I can say is \u2014 welcome back, Redis! We really did miss you.<\/p>\n\n\n\n<p>For more information, <a href=\"https:\/\/redis.io\/blog\/agplv3\/\" target=\"_blank\" rel=\"noreferrer noopener\">see the official announcement<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Redis in-memory data store returns to its open-source roots by adopting AGPLv3 in Redis 8 to address community concerns.<\/p>\n","protected":false},"author":10,"featured_media":167146,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,5],"tags":[3651,3748,3815,5755],"class_list":["post-167143","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software","category-news","tag-databases","tag-development","tag-redis","tag-valkey"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/posts\/167143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/comments?post=167143"}],"version-history":[{"count":0,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/posts\/167143\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/media\/167146"}],"wp:attachment":[{"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/media?parent=167143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/categories?post=167143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxiac.com\/wp-json\/wp\/v2\/tags?post=167143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}