Email or username:

Password:

Forgot your password?
Viktor Nagornyy

3 serious forks of to watch:

Mutli-threaded fork of Redis based on Redis 6.
BSD 3 Clause license.
Owned by Snapchat.
github.com/Snapchat/KeyDB

Recent fork by one person based on the last open source version of Redis 7.2.4.
On Codeberg.
LGPL 3.0 license.
codeberg.org/redict/redict

PlaceholderKV (searching for name)

Started by former Redis contributor(s) and AWS employees.
BSD 3 Clause license.
github.com/placeholderkv/place

Boosts appreciated šŸ™

11 comments
gunstick

@viktor tbose licenses should be changed in a way that they cannot be made closed source.

Federico DamiƔn Schonborn

@gunstick @viktor Redict has a LGPL license and a DCO, the only way to change the license is if every single developer and every contributor agrees

Julia

@viktor @rysiek Also: Garnet github.com/microsoft/garnet, MIT, Redis-compatible and created by Microsoft (this can be a good or a bad thing)

Viktor Nagornyy

@julia @rysiek That's not a fork though, but an open source alternative. Curious to see if it gains traction.

Ryan Hamel

@viktor@me.dm Why not DragonflyDB or Skytable, which have been around before the license change?

Christof Donat

@viktor

That's great, thank you. Does anybody know, what happened to Pedis (Parallel Redis)? It seems to be stalled.

Justin

@viktor I was really dreading this. Many forks pop up. People go to different ones and then you have no really solid one to choose from as the official successor.

Markus Wamser

@viktor Andrew Kelley has a good take on this: andrewkelley.me/post/redis-ren

tl;dr: Redis forked itself by doing the license change and the project's legitimate continuation is under the name Redict.

Alex

@viktor Kvrocks seems to be Redis compatible. Might be worth a look: github.com/apache/kvrocks

Go Up