Redis Rejects Open Source! Community says "Fork You Very Much!"

are you ready for this reddis a popular inmemory database used for caching has made some licensing changes that are causing a stir previously redus offered a permissive license that allowed anyone to use and modify the code freely under the BSD 3 license but now they've switched to a dual license model with much stricter terms this change didn't sit well with many developers including some who were core contributors to the project and in response some Forks have been made by different groups with different goals Source Hut for example has started a fork called redict or redict not sure and a group led by the Linux Foundation has created a fort called valky both redict and valky are based on the latest fully open- Source version of reddis which is 7.2.4 and aims to continue development under a more developer friendly license several major tech companies are also backing the valky branch or the valky fork including AWS Google and Oracle so what does this mean for you well if you're a casual redus user you might not need to worry too much in the short term because you can likely keep using the existing open source version for a while however if you're a developer who relies heavily on reddis you'll want to keep an eye on this situation rict is focusing on stability and maintenance while valky seems more ambitious for long-term evolution of the project but both could be viable Alternatives in the long run you may be wondering what is the difference between those two rict and valky well Drew default of rict has said that in technical terms by the way this is a quote from Drew in technical terms we are focusing on stability and long-term maintenance and on achieving Excellence within our current scope we believe that rict is near feature complete and that it is more valuable to our users if we take a conservative stance to Innovation and focus on long-term reliability Instead This is in part a choice we've made to distinguish ourselves from valky whose commercial interests are able to invest more resources into developing more radical Innovations but also an acknowledgement of a cultural difference between our projects and that the folks behind rict Place greater emphasis on software with a finite scope and Ambitions towards long-term stability rather than focusing on long-term growth and scope and complexity so that's the difference between valky and rict from the person who started rict now Microsoft has taken a different approach to this instead of for the code they've created their own redis compatible caching solution called Garnet so the world of inmemory databases is getting pretty interesting we have reddis with its new licensing the new forks rict and valky and Garnet the alternative from Microsoft ultimately the choice of which solution to use will depend on your specific needs and preferences and while no one can say what the outcome of this will be I don't think any of us were ready for this thanks for watching this clip from my show this week in Linux if you like it and want to see more then check out this episode of twill

Channel: Michael Tunnell

Views: 2,986

Keywords: Redis, in-memory database, caching, licensing, open source, closed source, permissive license, BSD, dual-license, developers, redis fork, SourceHut, Redict, Linux Foundation, Valkey, developer-friendly, AWS, Google, Oracle, Drew DeVault, Microsoft, Redis-compatible, Garnet, linux, linux news, open source news, open source software

Id: r67MRruNhow

Length: 3min 10sec (190 seconds)

Published: Sat Apr 06 2024