#database #server #client #key-value

bin+lib yedb

Rugged embedded and client/server key-value database

19 releases

new 0.0.19 Jun 19, 2021
0.0.18 Jun 18, 2021
0.0.15 May 30, 2021
0.0.3 Feb 24, 2021

#165 in Database interfaces

Download history 28/week @ 2021-02-24 10/week @ 2021-03-03 1/week @ 2021-03-10 1/week @ 2021-03-17 10/week @ 2021-03-24 7/week @ 2021-03-31 3/week @ 2021-04-07 21/week @ 2021-04-14 6/week @ 2021-04-21 3/week @ 2021-04-28 12/week @ 2021-05-05 12/week @ 2021-05-12 121/week @ 2021-05-19 51/week @ 2021-05-26 5/week @ 2021-06-02 47/week @ 2021-06-09

109 downloads per month



yedb - rugged embedded and client/server key-value database (Rust implementation)


  • Is it fast?

  • Rust version is pretty fast, except writes are still slow if auto-flush is enabled.

  • Is it smart?

  • No

  • So what is YEDB for?

  • YEDB is ultra-reliable, thread-safe and very easy to use.

  • I don't like Rust

  • There are other implementations.

Power loss data survive demo


YEDB is absolutely reliable rugged key-value database, which can survive in any power loss, unless the OS file system die. Keys data is saved in the very reliable way and immediately flushed to disk (this can be disabled to speed up the engine but is not recommended - why then YEDB is used for).

Rust version features

  • Rust version is built on top of Serde framework.

  • All key values are serde_json::Value objects.

  • Storage serialization formats supported: JSON (default), YAML, MessagePack and CBOR.

  • As byte type is not supported by serde_json::Value at this moment, Rust version can not handle byte key values.

  • Contains: embedded library, async server and command-line client (TCP/Unix socket only).

  • The command-line client is very basic. If you need more features, use yedb Python CLI.

Additional features over YEDB specs

  • "delete" command does not delete keys, they are moved to .trash folder instead

  • .trash folder is being cleaned when "purge" method is invoked.

  • "auto_bak" property tells server to automatically create backup key versions when key data is modified

  • "bak" keys are hidden


Binaries available at the releases page.

Run server:

./yedb-server /tmp/db1

Use client:

# get server info
./yedb-cli info
# set key value
./yedb-cli set x 5 -p number
# list all keys
./yedb-cli ls /
# edit key with $EDITOR
./yedb-cli edit x
# get key as JSON
./yedb-cli get x
# get help for all commands
./yedb-cli -h

Code examples

The database/client objects can be safely shared between threads using any kind of Lock/Mutex preferred.

Embedded example

use yedb::Database;
use serde_json::Value;

fn main() {
    let mut db = Database::new();
    let key_name = "test/key1";
    db.key_set(&key_name, Value::from(123u8)).unwrap();
    println!("{:?}", db.key_get(&key_name));

TCP/Unix socket client example

use yedb::YedbClient;
use serde_json::Value;

fn main() {
    let mut db = YedbClient::new("tcp://");
    let key_name = "test/key1";
    db.key_set(&key_name, Value::from(123u8)).unwrap();
    println!("{:?}", db.key_get(&key_name));

Cargo crate




Some benchmark data

  • CPU: Intel Core i7-8550U (4 cores)
  • Drive: Samsung MZVLB512HAJQ-000L7 (NVMe)
  • auto_flush: false
  • connection: Unix socket
  • server workers: 2
  • client threads: 4
set/number: 8164 ops/sec
set/string: 7313 ops/sec
set/array: 7152 ops/sec
set/object: 5272 ops/sec

get/number: 49709 ops/sec
get/string: 33338 ops/sec
get/array: 31426 ops/sec
get/object: 11654 ops/sec

get(cached)/number: 122697 ops/sec
get(cached)/string: 61206 ops/sec
get(cached)/array: 59309 ops/sec
get(cached)/object: 34583 ops/sec

increment: 7079 ops/sec


~417K SLoC