#key-value-database #key-value #ordered #serde #lexicographical #byte-sequences

no-std ordcode

Serialization format which preserves lexicographical ordering, for use with key-value databases

1 unstable release

0.2.2 Dec 25, 2020

#1265 in Encoding

MIT/Apache

86KB
2K SLoC

Build

ordcode

A set of primitives and Serde serializers for fast, prefix-free encoding which preserves lexicographic ordering of values.

It is intended for encoding keys and values in key-value databases.

OMG! Yet another serialization format?

In most existing designs, prefix-free encoding of byte sequences is performed by escaping "end-of-sequence" bytes. This takes extra space, and makes it difficult to know sequence length without processing the whole input buffer; this also complicates memory allocation for deserialized data. Instead, we take advantage of the fact that exact record size is always known in key-value databases. This implementation relies on "two-sided" buffer design: sequence lengths are varint-encoded and pushed to the tail end of the buffer, so it is possible to get original length of serialized byte sequence(s) by deserializing a few bytes only. For serialization, this implementation provides (very fast) calculation of exact size of serialized data length before serialization itself. These features enable effective and predictable buffer management for repetitive scans and no-heap (#[no-std]) targets.

Features

  • encodings in both ascending and descending lexicographic orderings are supported
  • encoding puts lengths of variable-size sequences to the end of serialized data, so resulting encoding is prefix-free and friendly to lexicographic ordering
  • zero allocations, supports #[no_std] environments
  • method to cheaply get exact size of serialized data without doing actual serialization, for effective buffer management
  • space-efficient varint encoding for sequence lengths and discriminants
  • easily customizable (endianness, encoding of primitive types etc.), with useful pre-sets
  • reader/writer traits for double-ended buffers, so you can implement your own or use implementations provided by the crate
  • no unsafe code

Cargo.toml features and dependencies

  • serde (on by default): include serde serializer and deserializer. If you need only primitives, you can opt out.
  • std (on by default): opt out for #[no-std] use, you will lose some convenience methods which use Vec<u8>

Stability guarantees

The underlying encoding format is simple and unlikely to change. As a safeguard, Serializer and Deserializer implement FormatVersion trait for all serializer parameter pre-sets (params::AscendingOrder, params::PortableBinary, params::NativeBinary).

Note: serializing with descending lexicographic order is particularly useful for key-value databases like rocksdb, where reverse iteration is slower than forward iteration.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~110–350KB