[HN Gopher] Warp: Lightweight Multi-Key Transactions for Key-Val...
       ___________________________________________________________________
        
       Warp: Lightweight Multi-Key Transactions for Key-Value Stores
        
       Author : yagizdegirmenci
       Score  : 34 points
       Date   : 2022-05-29 18:01 UTC (4 hours ago)
        
 (HTM) web link (muratbuffalo.blogspot.com)
 (TXT) w3m dump (muratbuffalo.blogspot.com)
        
       | NonNefarious wrote:
       | Here's a nitpick: It's key/value store, not key-value store.
       | 
       | A key-value store would only store "key values."
        
         | NonNefarious wrote:
         | I love how somebody modded INFORMATION down.
         | 
         | And here we were just making fun of Reddit for this kind of
         | infantile behavior.
        
           | nemothekid wrote:
           | Because it's bike shedding. The post is about some pretty
           | interesting database internals and a comment nitpicking about
           | the semantics of language, which have no relevance to the
           | article content, isn't constructive.
        
             | NonNefarious wrote:
             | Says the hypocrite who thinks the phrase "bike shedding" is
             | informative.
             | 
             | I can see why you're offended by grammatical information.
        
       | atombender wrote:
       | Warp is quite interesting, and seemed really promising and ahead
       | of its time. Unfortunately, Hyperdex has not been maintained for
       | many years [1]. While the technology is impressive, the author
       | seems to have lost interest, and moved on to working on something
       | called Consus [2], which has also been abandoned (no activity
       | 2018).
       | 
       | Hyperdex never became popular, and a problem all along was that
       | the author -- a very talented developer, from what I can tell --
       | seemed more invested in his projects from the perspective of
       | academic research (he developed Hyperdex at Cornell, I believe)
       | than in delivering a practical, living open source project. He
       | tried to form a company around Hyperdex (the transactional Warp
       | add-on was commercial) even though nobody seemed to be using it;
       | and he was the sole developer. I actually submitted a PR at one
       | point to fix a build problem, but the author was completely
       | unresponsive; you can't really do open source that way.
       | 
       | I _think_ the Warp code was actually open sourced when the author
       | realized they had failed to commercialize it, but I 'm not sure;
       | it's been a long time.
       | 
       | [1] https://github.com/rescrv/HyperDex/issues/233
       | 
       | [2] https://github.com/rescrv/Consus
        
       | jph wrote:
       | Nice: ACID guarantees; 75% of the throughput of the non-
       | transactional key-value store it builds upon; linear scaling;
       | conflict retries. Worth trying IMHO.
        
       | hbrundage wrote:
       | This system doesn't support interactive transactions does it? In
       | that the whole read / write set needs to be known up front before
       | a transaction can start being processed? I know that systems like
       | FoundationDB and Calvin/Fauna work similarly and get incredible
       | performance because sequencing is so much easier / lock free. I
       | think those two systems couldn't be adapted for interactive
       | transactions really (without client side retries) but maybe warp
       | could be which is cool!
        
         | voidmain wrote:
         | FoundationDB does interactive transactions.
        
       ___________________________________________________________________
       (page generated 2022-05-29 23:00 UTC)