This software is provided under a dual license. You may choose to use it under the terms of either:
1. GNU General Public License, Version 2 (GPLv2), or
2. GNU Affero General Public License, Version 3 (AGPLv3).
You may use, copy, modify, and distribute this software under the terms of either license, at your option. The full text of both licenses is included below for reference.
IANAL, but isn't GPLv2 strictly more permissive? Why would anybody ever not just pick to use it under that one and ignore AGPL?
It's weird that they don't mention similar distributed NewSQL databases like TiKV, which also has a MySQL layer (TiDB), and position themselves as a Redis replacement.
Interesting that it supports SQL transaction syntax. Does make it easier for traditional SQL users to switch to a Redis interface database as its primary store
Really appreciate it. I am the CEO of EloqData. We submitted the ShowHN about a year ago [1]. Since then we made a lot of progress, much of the work is based on the feedback from the great HN community, including:
1) Open Source (GPL and AGPL) (thanks PeterZaitsev).
2) Session based transaction in Redis API. (thanks fizx)
3) Better explanation of the architecture [2] (thanks apavlo).
4) Testing with Jepsen (internally, we will do it officially when we have the resource) (thanks jacobn, among others).
Again, thanks, really appreciate the community support. Please go to our website [3] or join our discord channel to provide more feedback.
I have tested EloqKV for a pet project and seems it is quite solid. Performance is fantastic, far out-performing most databases with durability by a large margin. I am not sure about the distributed transaction correctness but all my tests seem to indicate it works as advertised, which is very interesting because the other distributed NewSql databases are all rather slow. Haven't tried their SQL and Mongo solutions, but they also look quite interesting.
I tested it and achieved around 42K operations per second.
while it already serves as a in-memory key-value store to be a strong alternative to DragonflyDB, thanks to its multi-threaded architecture (each thread handles a separate keyspace, without any lock-based mutual-exclusion like KeyDB), it also goes beyond that and offers features like the transactional key-value operations and the persistence mechanisms.
10 comments
[ 2.3 ms ] story [ 30.9 ms ] thread1) Open Source (GPL and AGPL) (thanks PeterZaitsev).
2) Session based transaction in Redis API. (thanks fizx)
3) Better explanation of the architecture [2] (thanks apavlo).
4) Testing with Jepsen (internally, we will do it officially when we have the resource) (thanks jacobn, among others).
Again, thanks, really appreciate the community support. Please go to our website [3] or join our discord channel to provide more feedback.
[1] https://news.ycombinator.com/item?id=41590905
[2] https://www.eloqdata.com/blog/2025/07/14/technology
[3] https://eloqdata.com