5 ms·

In a sense valkey is the main line and redis is now the fork. Valkey is about the same except losing the trademark. It’s similar to Hudson and Jenkins. It’s not

In a sense valkey is the main line and redis is now the fork. Valkey is about the same except losing the trademark. It’s similar to Hudson and Jenkins. It’s not so clear cut with OpenSearch.

sroussey 2y ago
What’s valkey?
- benatkin 2y ago
  Persistent key-value database with network interface https://packages.debian.org/testing/database/valkey-server https://packages.debian.org/testing/database/valkey-server
- alanwreath 2y ago
  fork of redis https://github.com/valkey-io/valkey https://github.com/valkey-io/valkey just before the transition to their new source available licenses
  - sroussey 2y ago
    Ah thanks. Is this by AWS or similar?
    - simonw 2y ago
      Yes: https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community https://www.linuxfoundation.org/press/linux-foundation-launc... > Industry participants, including Amazon Web Services (AWS), Google Cloud, Oracle, Ericsson, and Snap Inc. are supporting Valkey.
      - benatkin 2y ago
        Interesting to see Google there. They have LevelDB.
        Octoth0rpe 2y ago
        I've only looked briefly at leveldb, but IIRC redis is _hugely_ more featureful than leveldb (which I'm sure is a great fit where it's used).
        scq 2y ago
        Redis and LevelDB are very different, with different use cases. LevelDB is a key-value storage library that writes to disk. It's the sort of thing you could use as the storage layer for a relational database. On the other hand, Redis is an in-memory key-value database server.
      - bitexploder 2y ago
        Cloud providers offer productized versions of Redis, so their interest in Valkey should be obvious :)
        bornfreddy 2y ago
        Yep. It is still a bit ironic that the community rallied behind Big Tech instead of a small startup though. Just saying.
        stephenr 2y ago
        The community rallied around a community fork with an open source licence instead of a VC funded startup with a penchant for changing licences.
        erik_seaberg 2y ago
        Around competitive prices and terms rather than a monopoly.
        acmeian 2y ago
        [dead]
        motorest 2y ago
        > Yep. It is still a bit ironic that the community rallied behind Big Tech instead of a small startup though. Just saying. The community rallied behind the project that ensures the software they care about remains free and open and available to all without the risk of being blind-sided.
        acmeian 2y ago
        Microsoft appears to be the only major player that isn't going with Valkey and established some sort of licensing deal with Redis [0]. [0]: https://redis.io/blog/introducing-azure-managed-redis https://redis.io/blog/introducing-azure-managed-redis
        riverdweller 2y ago
- simonw 2y ago
  It's the Redis fork with the most resources and the most backing. It's well funded and it sits under the Linux foundation: https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community https://www.linuxfoundation.org/press/linux-foundation-launc...
  - jonny_eh 2y ago
    and remains truly open-source, unlike Redis.
    - benatkin 2y ago
      Redis from Redis Labs, available under a choice of its own license or the SSPL, is pretty close to truly open-source, IMO closer to it than the BUSL, which is another source-available license. It is pretty similar to the AGPLv3, and they even credibly applied to get it OSI-approved. https://blog.tidelift.com/what-i-learned-from-the-server-side-public-license https://blog.tidelift.com/what-i-learned-from-the-server-sid... https://opensource.stackexchange.com/questions/11291/how-to-interpret-the-sspl-terms-on-licensing-the-service-under-sspl https://opensource.stackexchange.com/questions/11291/how-to-... What it isn't close to is the original license, which is a permissive open source license. The license switch-up is why a fork was needed. Matrix did a similar thing with the AGPL which alas, doesn't have a major fork. https://element.io/blog/element-to-adopt-agplv3/ https://element.io/blog/element-to-adopt-agplv3/ Although it's technically still open source, they didn't do right by the contributors to it.
      - jenadine 2y ago
        If the new license is so similar to the AGPL, why did they not pick AGPL as one of the license options in order to keep a well known OSI-aproved license?
        adolph 2y ago
        Yes, picking the same license is at least some security against a backdoor of some crafty IP lawyer.
antirez 2y ago
IMHO the "real" Redis is not about licensing, but about design (as long as the license is acceptable, as I think it is in both cases). We will see.
- benatkin 2y ago
  That’s a nice way of looking at it. It’s quite an influential project. I’m just now thinking of taking more direct inspiration from it for a micro-library for webassembly. I wish you success in Redis Labs and thanks for Redis. In my other comment I said I never considered using Redis under the new license, but I didn’t say that I never would consider it, and I think I would if I found myself on a project that needs a key value database with enterprise support or more bells and whistles. I think it has its place, and to me it is an awful lot like postgres and EnterpriseDB, especially if Redis Labs gives its blessing, directly or tacitly, to adding this new vector type to valkey.

In a sense valkey is the main line and redis is now the fork. Valkey is about the same except losing the trademark. It’s similar to Hudson and Jenkins. It’s not so clear cut with OpenSearch.

sroussey 2y ago

What’s valkey?

benatkin 2y ago
Persistent key-value database with network interface https://packages.debian.org/testing/database/valkey-server https://packages.debian.org/testing/database/valkey-server
alanwreath 2y ago
fork of redis https://github.com/valkey-io/valkey https://github.com/valkey-io/valkey just before the transition to their new source available licenses
- sroussey 2y ago
  Ah thanks. Is this by AWS or similar?
  - simonw 2y ago
    Yes: https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community https://www.linuxfoundation.org/press/linux-foundation-launc... > Industry participants, including Amazon Web Services (AWS), Google Cloud, Oracle, Ericsson, and Snap Inc. are supporting Valkey.
    - benatkin 2y ago
      Interesting to see Google there. They have LevelDB.
      - Octoth0rpe 2y ago
        I've only looked briefly at leveldb, but IIRC redis is _hugely_ more featureful than leveldb (which I'm sure is a great fit where it's used).
      - scq 2y ago
        Redis and LevelDB are very different, with different use cases. LevelDB is a key-value storage library that writes to disk. It's the sort of thing you could use as the storage layer for a relational database. On the other hand, Redis is an in-memory key-value database server.
    - bitexploder 2y ago
      Cloud providers offer productized versions of Redis, so their interest in Valkey should be obvious :)
      - bornfreddy 2y ago
        Yep. It is still a bit ironic that the community rallied behind Big Tech instead of a small startup though. Just saying.
        stephenr 2y ago
        The community rallied around a community fork with an open source licence instead of a VC funded startup with a penchant for changing licences.
        erik_seaberg 2y ago
        Around competitive prices and terms rather than a monopoly.
        acmeian 2y ago
        [dead]
        motorest 2y ago
        > Yep. It is still a bit ironic that the community rallied behind Big Tech instead of a small startup though. Just saying. The community rallied behind the project that ensures the software they care about remains free and open and available to all without the risk of being blind-sided.
        acmeian 2y ago
        Microsoft appears to be the only major player that isn't going with Valkey and established some sort of licensing deal with Redis [0]. [0]: https://redis.io/blog/introducing-azure-managed-redis https://redis.io/blog/introducing-azure-managed-redis
        riverdweller 2y ago
simonw 2y ago
It's the Redis fork with the most resources and the most backing. It's well funded and it sits under the Linux foundation: https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community https://www.linuxfoundation.org/press/linux-foundation-launc...
- jonny_eh 2y ago
  and remains truly open-source, unlike Redis.
  - benatkin 2y ago
    Redis from Redis Labs, available under a choice of its own license or the SSPL, is pretty close to truly open-source, IMO closer to it than the BUSL, which is another source-available license. It is pretty similar to the AGPLv3, and they even credibly applied to get it OSI-approved. https://blog.tidelift.com/what-i-learned-from-the-server-side-public-license https://blog.tidelift.com/what-i-learned-from-the-server-sid... https://opensource.stackexchange.com/questions/11291/how-to-interpret-the-sspl-terms-on-licensing-the-service-under-sspl https://opensource.stackexchange.com/questions/11291/how-to-... What it isn't close to is the original license, which is a permissive open source license. The license switch-up is why a fork was needed. Matrix did a similar thing with the AGPL which alas, doesn't have a major fork. https://element.io/blog/element-to-adopt-agplv3/ https://element.io/blog/element-to-adopt-agplv3/ Although it's technically still open source, they didn't do right by the contributors to it.
    - jenadine 2y ago
      If the new license is so similar to the AGPL, why did they not pick AGPL as one of the license options in order to keep a well known OSI-aproved license?
      - adolph 2y ago
        Yes, picking the same license is at least some security against a backdoor of some crafty IP lawyer.

antirez 2y ago

IMHO the "real" Redis is not about licensing, but about design (as long as the license is acceptable, as I think it is in both cases). We will see.

benatkin 2y ago
That’s a nice way of looking at it. It’s quite an influential project. I’m just now thinking of taking more direct inspiration from it for a micro-library for webassembly. I wish you success in Redis Labs and thanks for Redis. In my other comment I said I never considered using Redis under the new license, but I didn’t say that I never would consider it, and I think I would if I found myself on a project that needs a key value database with enterprise support or more bells and whistles. I think it has its place, and to me it is an awful lot like postgres and EnterpriseDB, especially if Redis Labs gives its blessing, directly or tacitly, to adding this new vector type to valkey.