6 ms·
BuffDB is a Rust library to simplify multi-plexing on edge devices
- deleted 2y ago[deleted]
- sgt 2y agoAnother local first library. The movement is taking off.
- jakjak123 2y agoWhat does "Simplify multiplexing on edge devices" even mean?
- 01HNNWZ0MV43FF 2y agoI guess they mean number of frontends times number of backends? https://github.com/buffdb/buffdb/issues/19 https://github.com/buffdb/buffdb/issues/19
- big_hacker 2y agoI 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 2y agoLike if you want your frontend to write to both Sqlite and RocksDB?
- jakjak123 2y agoIs 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 2y ago> protobuf such an awful format, I wish people would stop using it
- ithkuil 2y agoWhy? The format is not that bad. The binding/libraries OTOH are often awful and they often require unnecessary full-message deserialization
- 38 2y agonot 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
- cryptonector 2y agoSelf-describing is point-less for serializations. There is a great deal of history here. ASN.1 has self-describing encoding rules such as BER/DER/CER, XER (XML), JER (JSON), and GSER (never mind), and it has non-self-describing serializations like PER (packed encoring rules) and OER (octet encoding rules). XML and JSON are self-describing, naturally. FastInfoSet is a PER-based fast encoding for XML, because it turns out that XML is slow (imagine that). XDR is a non-self-describing serialization format that resembles OER but with 4-octet alignment. Flat buffers is essentially an OER-ish encoding for the same IDL as protobufs, and is much better than protobufs. It would be nice if the next serialization format either is truly original or just solves problems that somehow none of the many existing schemes do. How many serialization formats are there? See: https://en.wikipedia.org/wiki/Comparison_of_data-serialization_formats https://en.wikipedia.org/wiki/Comparison_of_data-serializati... (which is NOT a complete list).
- 38 2y ago> Self-describing is point-less for serializations you couldn't be more wrong. what happens when you lose the schema, or never had access to it in the first place? think from the point of view of reverse engineering
- ilayn 2y agoYet another title to drive embedded device designers and control engineers up the wall. Why don't you make up your own bullshit words instead of randomly picking stuff from other places? That's not even multiplexing.