4 releases

0.1.6 Jan 13, 2022
0.1.5 Jun 25, 2021
0.1.4 Oct 15, 2020
0.1.3 Dec 25, 2019

#728 in Database interfaces

Download history 5/week @ 2024-02-18 45/week @ 2024-02-25 46/week @ 2024-03-03 7/week @ 2024-03-10 1/week @ 2024-03-17 80/week @ 2024-03-31

90 downloads per month
Used in 2 crates

LGPL-3.0

41KB
991 lines

Build Status

FlumeDB

The Sunrise Choir Flume is a re-write of the JavaScript flumedb into Rust with a new architecture for better performance and flexibility.

Architecture

Flume is a modular database:

  • our main source of truth is an append-only write-only log: which provides durable storage
  • our secondary derived truths are views on the log: which focus on answering queries about the data
    • each view receives data through a read-only copy of the append-only log
    • each view can build up their own model to represent the data, either to point back to the main source of truth (normalized) or to materialize it (denormalized)
    • each view creates a structure optimized for the queries they provide, they don't need to be durable because they can always rebuild from the main log

In flume, each view remembers a version number, and if the version number changes, it just rebuilds the view. This means view code can be easily updated, or new views added. It just rebuilds the view on startup.

Example

use flumedb::Error;
use flumedb::OffsetLog;

fn main() -> Result<(), Error> {
    let path = shellexpand::tilde("~/.ssb/flume/log.offset");
    let log = OffsetLog::<u32>::open_read_only(path.as_ref())?;

    // Read the entry at offset 0
    let r = log.read(0)?;
    // `r.data` is a json string in a standard ssb log.
    // `r.next` is the offset of the next entry.
    let r = log.read(r.next);

    log.iter()
    .map(|e| serde_json::from_slice::<serde_json::Value>(&e.data).unwrap())
    .for_each(|v| println!("{}", serde_json::to_string_pretty(&v).unwrap()));

    Ok(())
}

Dependencies

~6–8.5MB
~145K SLoC