I evaluated it for a project last year, but decided not to use it. One reason was that at the time, the project seemed to have been abandoned; the author did not respond to issues or pull requests. Another was that based on Google searches, there seemed to be no one else actually using it in production; so even considering getting the commercial ACID support seemed like a big gamble, never mind that I couldn't find any info on how it performed in large clusters, and so on.

That said, it seemed technically brilliant, and fast.

If Escriva can accomplish the same thing with Consus, in a fully open source way, and gain traction enough to keep the project alive, I could see this as something I would consider using. That said, I'm wary of anyone who just abandons projects like that, without telling anyone about it.

> If Escriva can accomplish the same thing with Consus, in a fully open source way, and gain traction enough to keep the project alive, I could see this as something I would consider using.

Totally agree. I feel like there's a big void in the open-source world for this type of technology that has yet to be filled. There used to be FoundationDB and, well, we all know what happened there. CockroachDB is probably the only other active, open-source project right now that claims to have strong ACID guarantees for multi-database transactions. However, the team is not wholly focused on performance at this stage of development (which some of their early benchmarks demonstrate).

If Consus can retain some of the performance characteristics of Hyperdex while providing completely open source distributed transactions, it will be an absolute game changer.

It's promising, at least. I think a system like this would be the most useful if you're able to layer a query language on top of it, and apparently even FoundationDB (which had an SQL layer on top of a K/V store) didn't perform all that well. The Cockroach guys claim to have found a performant way of doing SQL on top of K/V, if I remember correctly, but we'll see. But having transactions in a distributed K/V store is certainly useful.

It does, but unless you know it is on top of a distributed KV store and design your schema and queries around that you will suffer horrible performance issues. Also, F1, similar to FDBs implementation, forces you to model your databases differently than you would in a "normal" oltp relational database.

I would be very surprised if anyone is still running their primary data store on "disks" that cares about performance. BTW, look at the design of F1 and you will see that they do object like hierarchical storage of related tables to ensure that they don't have to go cross partition for queries.