• dashcubeit@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 days ago

    For me it’s Keydb. Good backing and dead simple to set up for high availability with master-master replication

    • dragnucs@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      7 days ago

      Great to hear it is a good drop-in replacement. I’ve been using KeyDB, but seeing valkey is more actif, I may endup using it too.

      • Hyacin (He/Him)@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        Great to hear it is a good drop-in replacement

        DB compatibility breaks at a point though (7.x maybe? Going off fuzzy memory) … so if you’re migrating from that version it’s a little less “drop in” and more "oh shoot, this method doesn’t work either?!? :'( "

        Very happy after the ‘migration’ though!

  • eldavi@lemmy.ml
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    8 days ago

    why does there need to be an alternative? is there something wrong or inefficient with it? is it just too old?

    • Daniel Quinn@lemmy.ca
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      8 days ago

      My guess is it’s the license change. From Wikipedia:

      In 2018, some modules for Redis adopted the SSPL. In 2024, the main Redis code switched to dual-licensed under the Redis Source Available License v2 and the Server Side Public License v1.

      Valkey appears to be a Redis fork that was triggered by the license change, but since Valkey still uses the original BSD license, I’m not sure I’d favour it over Redis since the latter switched licences specifically to prevent abuse of the BSD license by parties like Amazon.