Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)

github.com

Post reply on HN
Print view View original

41–46 of 46 posts

Re: EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)

#41

Post by sitkack »

the_precipitate wrote: post #26

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,…

You need to take a look at https://github.com/aerospike/aerospike-server sub millisecond reads and writes and supports transactions. Its main competitor is ScyllaDB which has comparable performance.

Re: EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)

#42

Post by the_precipitate »

sitkack wrote: post #41
the_precipitate wrote: post #26

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,…

You need to take a look at https://github.com/aerospike/aerospike-server sub millisecond reads and writes and supports transactions. Its main competitor is ScyllaDB which has comparable performance.

Thanks! I remember that for a long time Aerospike didn’t support transactions, and I just found out they rolled out this feature just a few months ago. I’ve always been a bit suspicious of NoSQL databases that add transaction support late in their lifecycle. MongoDB seems to fall into the same category, and its transaction support is, to say the least, rather unsatisfying.

Re: EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)

#43

Post by the_precipitate »

coolspot wrote: post #37
iamlintaoz wrote: post #19

Earlier quoted context omitted.

The reason is because we use a layer (our main innovation) called DataSubstrate to build modular databases that support distributed transactions [1]. Because we use some MariaDB code (GPLv2) and some MongoDB code (AGPLv3) in our other projects [2] [3], so we license our DataSubstrate code to be compatible with both, and therefore, we also license EloqKV under both licenses. [1] https://www.eloqdata.com/blog/2025/07/1…

I don’t think end users can pick a license because you have pieces licensed under GPLv2 and AGPLv3 . They will have to obey by both, which is tricky if they are conflicting.

My understanding is that they have a common layer over which they hold full copyright, so they can license it however they like. But since this software is also used in EloqSQL (which includes MariaDB code) and EloqDoc (which includes MongoDB code), the license has to be compatible with both. That’s why they state that the code can be licensed under either license (note the OR part).

I doubt they would accept any code that cannot be re-licensed, because the common layer essentially “transmits the infection,” for lack of a better way to describe it.

Re: EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)

#44

Post by mo_abdallah0 »

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.

Re: EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)

#45

Post by netpaladinx »

mo_abdallah0 wrote: post #44

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.

I like the thread per core model. EloqKV, DragonflyDB, ScyllaDB all follow this pattern.

Re: EloqKV, a distributed database with Redis compatible API (GPLv2 and AGPLv3)

#46

Post by sitkack »

the_precipitate wrote: post #42
sitkack wrote: post #41

Earlier quoted context omitted.

You need to take a look at https://github.com/aerospike/aerospike-server sub millisecond reads and writes and supports transactions. Its main competitor is ScyllaDB which has comparable performance.

Thanks! I remember that for a long time Aerospike didn’t support transactions, and I just found out they rolled out this feature just a few months ago. I’ve always been a bit suspicious of NoSQL databases that add transaction support late in their lifecycle. MongoDB seems to fall into the same category, and its transaction support is, to say the least, rather unsatisfying.

What they rolled out was multikey transactions, they previously only had single key. Between multikey and session consistency, Aerospike is pretty nice.
Post reply on HN