[HN Gopher] BuffDB is a Rust library to simplify multi-plexing o...
       ___________________________________________________________________
        
       BuffDB is a Rust library to simplify multi-plexing on edge devices
        
       Author : opensourcemaxi
       Score  : 37 points
       Date   : 2024-08-25 16:34 UTC (6 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | sgt wrote:
       | Another local first library. The movement is taking off.
        
       | jakjak123 wrote:
       | What does "Simplify multiplexing on edge devices" even mean?
        
         | 01HNNWZ0MV43FF wrote:
         | I guess they mean number of frontends times number of backends?
         | https://github.com/buffdb/buffdb/issues/19
        
         | big_hacker wrote:
         | I think it's a proxy between your software and SQLite with a
         | new database API. I guess "multiplexing" is a big word for
         | saying you can someday swap SQLite for something else.
         | 
         | The CLI shows key-value store features.
         | 
         | I don't know if this software has real world savings in
         | performance. I don't think I would ever use this software.
        
           | jakjak123 wrote:
           | Like if you want your frontend to write to both Sqlite and
           | RocksDB?
        
       | jakjak123 wrote:
       | Is it a protobuf based database store, or is it a database that
       | uses grpc as its connection communication? Could be a bit clearer
       | from the frontpage
        
         | 38 wrote:
         | > protobuf
         | 
         | such an awful format, I wish people would stop using it
        
           | ithkuil wrote:
           | Why?
           | 
           | The format is not that bad.
           | 
           | The binding/libraries OTOH are often awful and they often
           | require unnecessary full-message deserialization
        
             | 38 wrote:
             | not self describing. if it was just the field names I could
             | deal with that, but even the values are ambiguous, since
             | the same type is used for Bytes and embedded Messages. the
             | worst part is the wire type integer has two unused values,
             | so they easily could have added a wire type for embedded
             | messages
        
       ___________________________________________________________________
       (page generated 2024-08-25 23:00 UTC)