Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance
by lobster_johnson on Sunday July 23, 2017 @08:17PM
(#14835097)
Hyperdex is no longer maintained [1]. While the technology is impressive, the author seems to have lost interest, and is now working on something called Consus [2].
Hyperdex's problem all along was that the author — a very talented developer from what I can tell — seems more invested in his projects from the perspective academic research (he's at Cornell) than in delivering a practical, living open source project. He tried to form a company around Hyperdex (the transactional "Warp" add-on thing was commercial) even though nobody seemed to be using it; and he was the sole developer. Unfortunately, as interesting as Consus is, history seems to be repeating itself there.
But yeah, Hyperdex seemed to have real potential at one point. It was the only NoSQL K/V store (at the time) that had transactions.
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance
by misframer on Sunday July 23, 2017 @09:45PM
(#14835377)
> It was the only NoSQL K/V store (at the time) that had transactions.
What about FoundationDB?
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance
by lobster_johnson on Monday July 24, 2017 @08:06AM
(#14837728)
Not open source, though.
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance
by misframer on Monday July 24, 2017 @11:46AM
(#14839426)
Warp wasn't open source either.
Re:Redis on Acid: 0.5M ops/sec, 1ms latency and ACID compliance
by lobster_johnson on Monday July 24, 2017 @11:51AM
(#14839469)
Good point, but at least you could try out Hyperdex and consider whether you wanted transactions. But this is pretty moot at this point, unless someone picks up Hyperdex development again.
[1] http://hyperdex.org/ [2] https://www.cs.cornell.edu/people/egs/papers/hyperdex-sigcom... [3] http://rescrv.net/papers/warp-tech-report.pdf