Use case

A key-value store that travels.

An ordered key-value store with one writer, kept in a signed log. A peer that holds a replica of the log opens it read-only and sees the same state.

The pieces

The libraries this needs. Each has install steps and a compiled example in its docs.

How it goes

  1. Every put is an entry

    kolo-kv writes each Put and Delete as one entry in a kolo-log log stored with kolo-store.

  2. The state is an index

    When the store opens, it rebuilds its index from the log and checks it against the log's signed head.

  3. Readers get the same state

    A peer with a replica, kept up to date by kolo-sync, opens it read-only and gets the same keys and values. No extra protocol.

Good to know

One writer per store. A deleted key's name stays in its delete entry, so keep secrets in values, not in keys. Deletion is best effort: a peer that already had the entry key can keep it.

Next