It's not right to say that Redis "had nothing to do with its development." They were a major contributors and were managing the project for many years. The problem like many other open source project is that the…
https://github.com/dragonflydb/dragonfly Is a multi-threaded drop in replacment
Sure. You can do that. But the community needs a single standard. Open standard that all in-memory data stores like Redis, ValKey, DragonflyDB, KeyDB, Kvrocks will support. Otherwise you will end up in a vendor lock.
We @Dragonfly had BSL right from start. I think it makes most sense for todays infrastructure echsystem.
HA already supported since v1.0. Dragonfly is released under BSL1.1. Its free for use in most cases. https://www.dragonflydb.io/docs/about/faq
All, My name is Oded Poncz, I am the CEO of DragonflyDB. Our goal with the FAQ was to aggragate valuable information for our community. We will take all the valuable feedback from this thread and improve. Thank you all…
hmm, Redis Labs are setting a cluster of 40 Redis processes on the same instance. It would be extremely difficult to do that with Redis OSS for anyone else.
The Change Date specifies when the source file changes from BSL to the specified Open Source license. Its always in the future.
GPL is copyleft and more restrictive in some elements. BSL 1.1 is actually quite popular nowdays.
Yes
Modern as the entire architecture is based on papers from the last few years. But also the first commit :)
Actually snapshot is done in the background and does not use fork like Redis. You can see it here: https://github.com/dragonflydb/dragonfly#memory-efficiency-b...
It's not right to say that Redis "had nothing to do with its development." They were a major contributors and were managing the project for many years. The problem like many other open source project is that the…
https://github.com/dragonflydb/dragonfly Is a multi-threaded drop in replacment
Sure. You can do that. But the community needs a single standard. Open standard that all in-memory data stores like Redis, ValKey, DragonflyDB, KeyDB, Kvrocks will support. Otherwise you will end up in a vendor lock.
We @Dragonfly had BSL right from start. I think it makes most sense for todays infrastructure echsystem.
HA already supported since v1.0. Dragonfly is released under BSL1.1. Its free for use in most cases. https://www.dragonflydb.io/docs/about/faq
All, My name is Oded Poncz, I am the CEO of DragonflyDB. Our goal with the FAQ was to aggragate valuable information for our community. We will take all the valuable feedback from this thread and improve. Thank you all…
hmm, Redis Labs are setting a cluster of 40 Redis processes on the same instance. It would be extremely difficult to do that with Redis OSS for anyone else.
The Change Date specifies when the source file changes from BSL to the specified Open Source license. Its always in the future.
GPL is copyleft and more restrictive in some elements. BSL 1.1 is actually quite popular nowdays.
Yes
Modern as the entire architecture is based on papers from the last few years. But also the first commit :)
Actually snapshot is done in the background and does not use fork like Redis. You can see it here: https://github.com/dragonflydb/dragonfly#memory-efficiency-b...