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.
Its available on Dragonfly https://github.com/dragonflydb/dragonfly Here is the docs https://www.dragonflydb.io/docs/command-reference/hashes/hex...
The figma route is exactly the case were the cost of service is very low. It make sense for Figma to offer a free tier because it costs them almost nothing. But when you have to keep the data available in submillisecond…
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…
KeyDB is a fork of Redis, whereas Dragonfly introduces a brand-new architecture, crafted from the ground up utilizing a share nothing, multi-threaded design. It implements both Redis and memcached APIs
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.
License is standard BSL 1.1. which means you can use it in production for your own workloads as long as you do not provide DF as a managed service.
Yes
In Redis cluster the client needs to be connected to all shards and manage those connections. Multi-key operation on different slots are not supported etc... Maintaining a cluster is not a fun responsibility. DF saves…
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...
I assume DF has the same performance as Memcached. It would be great if someone makes this benchmark and share.
DF also has a noval eviction algorithm that combines LRU and LFU which could be great for caching use cases.
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.
Its available on Dragonfly https://github.com/dragonflydb/dragonfly Here is the docs https://www.dragonflydb.io/docs/command-reference/hashes/hex...
The figma route is exactly the case were the cost of service is very low. It make sense for Figma to offer a free tier because it costs them almost nothing. But when you have to keep the data available in submillisecond…
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…
KeyDB is a fork of Redis, whereas Dragonfly introduces a brand-new architecture, crafted from the ground up utilizing a share nothing, multi-threaded design. It implements both Redis and memcached APIs
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.
License is standard BSL 1.1. which means you can use it in production for your own workloads as long as you do not provide DF as a managed service.
Yes
In Redis cluster the client needs to be connected to all shards and manage those connections. Multi-key operation on different slots are not supported etc... Maintaining a cluster is not a fun responsibility. DF saves…
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...
I assume DF has the same performance as Memcached. It would be great if someone makes this benchmark and share.
DF also has a noval eviction algorithm that combines LRU and LFU which could be great for caching use cases.