A modern replacement for Redis and Memcached (by dragonflydb)

Dragonfly Alternatives

Similar projects and alternatives to dragonfly

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better dragonfly alternative or higher similarity.

dragonfly reviews and mentions

Posts with mentions or reviews of dragonfly. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-22.
  • Redict is an independent, copyleft fork of Redis
    3 projects | news.ycombinator.com | 22 Mar 2024
    https://github.com/dragonflydb/dragonfly is another option. Not a fork but API-compatible reimplementation.
  • Redis License Changed
    11 projects | news.ycombinator.com | 20 Mar 2024
    Check out DragonflyDB (BSL): https://www.dragonflydb.io/

    BSL is not OSI-approved, but it’s a much more reasonable AWS-resistant license. It’s the same license CockroachDB uses, for example.

    KeyDB (BSL, acquired by Snapchat) is also an option: https://keydb.dev/

    BSL is a much better license, but it’s a gamble on how long KeyDB will be supported. I don’t want to mess around with such a core part of my architecture.

    11 projects | news.ycombinator.com | 20 Mar 2024
  • Dragonfly Cache Design
    2 projects | dev.to | 18 Jul 2023
    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
    5 projects | news.ycombinator.com | 15 Jun 2023
    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...

  • Dragonfly – The most performant in-memory data store on Earth
    4 projects | news.ycombinator.com | 21 May 2023
    2. You are right, I need to shut the fuck up and let self-righteous hn crowd with torches do what they do best - find a weakness, and push it until they get bored and switch to beat another builder. You asked me about my perspectives and priorities? These are my priorities: https://github.com/dragonflydb/dragonfly/graphs/contributors
    4 projects | news.ycombinator.com | 21 May 2023
    > Developers do not want to manage a cluster of single cpu processes. Not on their laptops and not in the production. And it's not just about management complexity. See this https://github.com/dragonflydb/dragonfly/issues/1229 and it's just one example. Single cpu - is just not enough for today use-cases.

    That may all very well be the case – let us assume it is for the sake of the argument although I have some comments about that as well – but that still means the argument is "Redis is too complex to run on multiple CPUs" and/or "Redis is poor for these workloads" (I didn't investigate that issue in-depth), and not "Redis is unable to do much work with this very powerful AWS instance". There two are very different things. There is no nuance anywhere in the benchmark. A reader might very well believe that this is all the performance they're going to get out of Redis on that machine, which that's clearly not the case.

    4 projects | news.ycombinator.com | 21 May 2023
    License is important: https://github.com/dragonflydb/dragonfly/blob/main/LICENSE.m...

    Dragonfly Business Source License 1.1

    License: BSL 1.1

    Licensor: DragonflyDB, Ltd.

    Licensed Work: Dragonfly including the software components, or any portion of them, and any modification.

    Change Date: March 15, 2028

    Change License: Apache License, Version 2.0, as published by the Apache Foundation.

    Additional Use Grant: You may make use of the Licensed Work (i) only as part of your own product or service, provided it is not an in-memory data store product or service; and (ii) provided that you do not use, provide, distribute, or make available the Licensed Work as a Service. A “Service” is a commercial offering, product, hosted, or managed service, that allows third parties (other than your own employees and contractors acting on your behalf) to access and/or use the Licensed Work or a substantial set of the features or functionality of the Licensed Work to third parties as a software-as-a-service, platform-as-a-service, infrastructure-as-a-service or other similar services that compete with Licensor products or services.

    4 projects | news.ycombinator.com | 21 May 2023
    Nokia was designed as strongest and most affordable phone, yet you use Iphone that costs 1000$. it's not about how it was designed but whether it addresses your current needs. Developers do not want to manage a cluster of single cpu processes. Not on their laptops and not in the production. And it's not just about management complexity. See this https://github.com/dragonflydb/dragonfly/issues/1229 and it's just one example. Single cpu - is just not enough for today use-cases.
  • The first version of Redis, written in Tcl
    6 projects | news.ycombinator.com | 18 May 2023
    I think this is relevant... These are 3 OSS databases that can be an alternative to Redis:

    - KeyDB: https://github.com/snapchat/keydb

    - Dragonfly: https://github.com/dragonflydb/dragonfly

    - Skytable: https://github.com/skytable/skytable

    I have used keyDB before. The raft consensus makes building an HA Redis easy.

  • A note from our sponsor - InfluxDB
    www.influxdata.com | 16 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →


Basic dragonfly repo stats
1 day ago

dragonflydb/dragonfly is an open source project licensed under BSL 1.1 which is not an OSI approved license.

The primary programming language of dragonfly is C++.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives