|
|
|
|
|
by jpc0
816 days ago
|
|
All this hinges in redis being a for profit with OSS software and not competing with AWS, that isn't happening though AWS won't happily fund their competitors and definitely wont contribute developer time to it. Redis is partly where it is because of large FAANG companies contributing to redis, that cannot be discounted. I don't have the time but go strip out all commits from FAANG companies employee and see if redis would be the product it is currently. I'm not saying AWS is right but at the same time that is what redis decided to allow when they used the model they did. Now that they see they could be making a ton of money they want to retroactively change their licensing which is arguably also bad. It's a money grab both ways which is what I have an issue with. I'm pretty sure we will see AWS fork redis just before the license change and keep developing from there. They could even also then have all new code be proprietary as far as the current license allows that. My argument is the industry in general is probably going to be worse of after this move than before. |
|
Redis is offered as a managed offering by AWS and other because it was already very popular between developers that were clients or potential clients of cloud vendors. That it is/was used also by FAANG companies doesn't change a thing in this part of the story. (And no, I don't believe Redis is popular because it was used by FAANG companies which also contributed back)