dragonfly
1store
Our great sponsors
dragonfly | 1store | |
---|---|---|
49 | 2 | |
23,791 | 1,307 | |
6.1% | - | |
9.9 | 10.0 | |
about 22 hours ago | over 4 years ago | |
C++ | C++ | |
BSL 1.1 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dragonfly
-
Redict is an independent, copyleft fork of Redis
https://github.com/dragonflydb/dragonfly is another option. Not a fork but API-compatible reimplementation.
- Redis License Changed
-
Scaling Real-Time Leaderboards with Dragonfly
Our journey will involve leveraging the capabilities of Dragonfly, a highly efficient drop-in replacement for Redis, known for its ultra-high throughput and multi-threaded share-nothing architecture. Specifically, we'll be utilizing two of Dragonfly's data types: Sorted-Set and Hash. These data structures are perfect for handling real-time data and ranking systems, making them ideal for our leaderboards.
-
Announcing Dragonfly Search
2023 has been a year with remarkable advancements in AI capabilities, and at Dragonfly, we are thrilled to power new use cases with our latest release: Dragonfly Search. This new feature set, debuting in Dragonfly v1.13, is a subset of RediSearch-compatible commands implemented natively in Dragonfly, allowing for both vector search and faceted search use cases in the highly scalable and performant Dragonfly in-memory data store.
- Dragonfly v1.10.0
-
Dragonfly Cache Design
If you have not heard about Dragonfly - please check it out. It uses - what I hope - novel and interesting ideas backed up by the research from recent years [1] and [2]. It's meant to fix many problems that exist with Redis today. I have been working on Dragonfly for the last 7 months and it has been one of the more interesting and challenging projects I've ever done!
-
Generating Income from Open Source
I recently ran across the the license for Dragonfly [1] which has some restrictions (rights reserved), but 5 years after the license date the license switches to Apache 2.0. Basically a timed-limited rights reservation. I don't hate it. I might even contribute to such a project for free.
I would consider something like this: When I release code, it's rights reserved for 5 years, then open-source (and this baked into an irrevocable license). Anyone may use the software for non-commercial purposes. Anyone may contribute, those who contribute will be granted permission for commercial use if I deem their contributions significant enough. Anyone may distribute the software under these terms.
If such a model became popular, I have a hard time imagining it could make things any worse. It might even accelerate open-source development. You might say, "but it's not open-source", fair enough, but we can view it as open-source contribution with a delay. For example, if this model became wildely popular this year, and we saw great progress with this model, then come 2028 we would be flooded with new open-source software and ultimately might be better off than it would have been without this model.
(And this whole thing makes me rethink copyright and patents and how much they really contribute to society. Perhaps they should be shortened?)
[1]: https://github.com/dragonflydb/dragonfly/blob/main/LICENSE.m...
- dragonflydb/dragonfly: A modern replacement for Redis and Memcached
-
Redis HA on k8s without Sentinel?
Maybe check out https://www.dragonflydb.io/ It claims to have a full redis implementation.
- Dragonfly is about 10x slower than Redis
1store
-
So, you call yourself the fastest key/value store? It's 5X, 10x and 25X faster
How about including Pedis in this? It is a Redis partial reimplementation, written around Seastar: https://github.com/fastio/1store
-
Redis Cluster Re-Implemented in Rust: Scaling Redis Easily in Kubernetes
There is a parallel but less fancy reimplementation of Redis called Pedis:
https://github.com/fastio/1store
It's built using Seastar, which is sort of an ugh but cool unholy marriage of node.js and C++ ;-). It predates C++20 coroutines I guess, so you pass callbacks around like in Node. Maybe they have updated that by now.
They have also done a version of memcached using DPDK. I don't see a Pedis one, but check out their memcached one (scroll down): http://seastar.io/
What are some alternatives?
KeyDB - A Multithreaded Fork of Redis
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
skytable - Skytable is a modern scalable NoSQL database with BlueQL, designed for performance, scalability and flexibility. Skytable gives you spaces, models, data types, complex collections and more to build powerful experiences
undermoon-operator - Kubernetes Operator for Redis cluster based on Undermoon
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
undermoon - Mordern Redis Cluster solution for easy operation.
Memcached - memcached development tree
sky-benches - Attempts at benchmarking Skytable with the others to see where we stand
Aerospike - Aerospike Database Server – flash-optimized, in-memory, nosql database
glommio - Glommio is a thread-per-core crate that makes writing highly parallel asynchronous applications in a thread-per-core architecture easier for rustaceans.