attache
dragonfly
| attache | dragonfly | |
|---|---|---|
| - | 52 | |
| 203 | 26,856 | |
| - | 3.2% | |
| 0.0 | 9.9 | |
| over 4 years ago | 5 days ago | |
| Ruby | C++ | |
| MIT License | BSL 1.1 |
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.
attache
We haven't tracked posts mentioning attache yet.
Tracking mentions began in Dec 2020.
dragonfly
-
Kronotop: Redis-compatible, transactional document store backed by FoundationDB
Other API-compatible reimplementations (others?):
https://github.com/dragonflydb/dragonfly DragonflyDB (not open source, BuSL-1.1) with more performance
https://github.com/apache/kvrocks Apache Kvrocks (Apache-2.0) uses disk-based NoSQL database to lower memory usage
- Databases in 2024: A Year in Review
-
Valkey achieved one million RPS 6 months after forking from Redis
This is impressive work, but it highlights redis biggest design flaw: single threadedness.
I recently discovered dragonflydb[1] that is 100% redis compatible, but designed from the get-go to be multi threaded - and thus its performance gains are even bigger. I imagine it being designed for multi threadedness from the beginning allows it to offer better performance long term, but that's just anyone's guess.
1: https://github.com/dragonflydb/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...