A persistent storage system

Clone this repo:


  1. d1d18c5 Disable suspicious tests in BTreeUtilsTest by Brian Goldman · 2 days ago master
  2. 3d1335e Disabling tests with undefined behavior by Brian Goldman · 2 days ago
  3. 70627be Adding trace for commit upload. by Benjamin Lerman · 4 days ago
  4. fa8eb56 Use ftl::Apply in asynchronous callbacks. by Benjamin Lerman · 4 days ago
  5. dd3a7ee Allow multiple executions of put benchmark app. by Nelly Vouzoukidou · 5 days ago
88                       88
88                       88
88                       88
88   ,adPPYba,   ,adPPYb,88   ,adPPYb,d8   ,adPPYba,  8b,dPPYba,
88  a8P_____88  a8"    `Y88  a8"    `Y88  a8P_____88  88P'   "Y8
88  8PP"""""""  8b       88  8b       88  8PP"""""""  88
88  "8b,   ,aa  "8a,   ,d88  "8a,   ,d88  "8b,   ,aa  88
88   `"Ybbd8"'   `"8bbdP"Y8   `"YbbdP"Y8   `"Ybbd8"'  88
                              aa,    ,88


What is Ledger?

Ledger is a distributed storage system for Fuchsia.

Each application (or more precisely, each component) running on behalf of a particular user has a separate data store provided and managed by Ledger, and vended to a client application by Fuchsia framework through its component context.

The data store for the particular component/user combination is private - not accessible to other apps of the same user, and not accessible to other users of the same app.

Each data store is transparently synchronized across devices of its user through a [cloud provider]. Any data operations are made offline-first with no coordination with the cloud. If concurrent modifications result in a data conflict, the conflict is resolved using an app-configurable merge policy.

Each data store is organized into collections exposing a key-value store API called pages. Page API supports storing data of arbitrary size, atomic changes across multiple keys, snapshots and modification observers.

See docs for documentation.

Repository contents