Valkey is the way for me...not that much to think or consider...
Can you expand on the high points from your perspective? Thanks.
Redis is forked
31–40 of 206 posts
Re: Redis is forked
#32Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…
> Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on top of their free open-source product and resell it, making tens of millions of dollars per day in the process. I can't really blame them. I won't blame them for regretting their past actions, but I hope the lesson would be learned: if you want to put limitation on the use of your software, you shouldn't have licensed…
With the noise people make when you don't use an OSI open-source license, little wonder. But when Redis started I think we didn't yet boardly understand the limitations of OSI licenses in the era of big tech cloud computing.
To people starting projects today, you have no excuse, we know better. Don't use OSI open-source unless it's entirely a labor of love that you're giving away free.
OSI Open-source business models are dead. Don't make that mistake.
Re: Redis is forked
#33I thought the author was bringing in genAI for little reason...then I clicked through. For some reason storing vectors and chats is core to Redis' vision of its future. ( https://redis.io/blog/the-future-of-redis/ ) I'm, generally, a mobile dev so I'm not familiar with redis. My handwave-y understanding is its a in-memory key/value DB. I don't understand how that brings anything to the table for genAI. Couldn't the p…
Redis will be used for genAI as it's always used: answer queries faster. Users are not interesting in waiting, answers need to be immediate. Plus reducing load on whatever you got behind Redis is a nice bonus.
I did evaluate a few vector databases for our RAG PoCs with quite a significant amount of metadata for permission handling on both the vector and the query, and execution time was in the area of milliseconds as far as I remember. The RAG performance hit pales in comparison to what computing time larger LLMs need, so I am not sure you are on the right track here.
Re: Redis is forked
#34Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…
>> Generally my stance with these forks born from community drama is "wait and see."
Whats funny about this one is as follows:
1. The license: BSD? LGPL? Do both... nothing says that you cant make the product available under both licenses. You prevent another rug pull...
2. The platform: Do both, Run the thing on GitHub like it always has been and back it up to the other platform. If MS makes GitHub into the next source forge... then you're already half way out.
3. The name: Not a hill any one should die on. Pick three, ask amazon legal to clear them or FSF legal to clear them and vote. Redict and valkey are both fucking stupid names... Yea you might have to live with storage mcstoreface but that would be better than either of the current options.
As for FOSS drama... Lacking any clear leadership, peoples ability to self organize is limited. These sorts of things happen all the time (systemd, x vs waylaid, how many unix forks?) The winning side is almost always the one with clear leadership.
Re: Redis is forked
#35Why, unlike Redis and Elasticsearch and Terraform, was there no big community fork of MongoDB when it was relicensed?
Cockroach, Materialize, and MariaDB were all also relicensed without massive backlash, I think. But I think that's because they had fewer users at the time.
But Mongo's was the one relicense event that didn't produce so much shock that a new fork came out of it. And Mongo's stock is doing great, if that's a good proxy for their overall success.
I wonder what the difference is.
Re: Redis is forked
#36Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…
> people won't want AWS/GCP/Azure to slap a UI on top of their free open-source product and resell it If it wasn't open-source it won't be as popular as it is in the first place, Redis is also using ton of open source software or libraries for free. Not defending AWS/GCP/Azure, I actually got my software used when i was young by a large company for free (not even a mention- Still using it i think, 5M+ Play Store Down…
Open Source is, by and large, intended by the creator to donate their ideas to benefit humanity as a whole; many people feel that using their thing to help strengthen an (ethically questionable) monopoly is acting against that core goal.
Re: Redis is forked
#37[flagged]
Re: Redis is forked
#38Generally my stance with these forks born from community drama is "wait and see." Sometimes the fork will gain traction and become the de facto "true" version (see Hudson -> Jenkins). Sometimes the fork will flop and people will largely stick to the original despite whatever caused the schism (see Terraform -> OpenTofu). Many of these recent forks are being done because people won't want AWS/GCP/Azure to slap a UI on…
Part of the bet is probably that since Terraform is almost necessarily going to run on a cloud service that is already being paid for, the user might not care that a bit gets added to the bill.
Redis? I'm not sure. Like you say, they don't want Big Tech to slap a UI on it and profit. And, really, once they start competing on price (which they might sooner rather than later to keep people from going back to on-prem) you can guess they might use something that's free so they don't have to pay the license on a per-server instance.
Re: Redis is forked
#39at work we're still at the pre-fork drama version of elasticsearch, it works and leaves us open to pick whichever direction we want to go at a later date when we need it. The same will be for redis, it works, no need to stay up to date.
Re: Redis is forked
#40Earlier quoted context omitted.
Pay up or roll your own. Nobody owes you free labor.
Nobody owes you free labor, but it's a world of uncertainty. People don't like uncertainty. Will this labor be priced reasonably, at around the same level that I value it, or will they pull a vmware and ask for my first born?
There’s no greater certainty than rolling your own and building your own stack.
If you want perfect reliability, use the standard library of a language and nothing else. It’s actually possible.
Ironically, the best open source projects are the ones that have no other dependencies beyond the standard library.