LiveStore

Open-source client-side data layer: a reactive SQLite store with an event-sourcing-based sync engine, built by johannes-schickling with Nicholas Schiefer and Geoffrey Litt rethinking-data-client-event-sourcing. The concrete artifact behind this spoke’s local-first entry.

How it works

The client holds a SQLite database with reactivity — queries re-run when the underlying data changes, so the UI binds directly to the store. State arrives as an immutable event log that syncs between clients and gets materialized into the local SQLite tables. The database is a derived view; the log is what travels.

That choice is the point of comparison with the CRDT frameworks (Automerge, Yjs, Loro) and with the query-sync engines (ElectricSQL, PowerSync, Zero): three different answers to what a sync engine should move over the wire.

Because the log and the materialized file are both user-holdable, data export is a property of the architecture rather than a feature — either the events or the SQLite database can be handed to the user.

Status

Known here only through one podcast interview with its own maintainer: no version, licence detail, adoption numbers, or independent evaluation. Overtone, Schickling’s music-curation app, is the reference deployment named.

Related

event-sourcing · local-first-architecture · johannes-schickling · rethinking-data-client-event-sourcing · turso · operational-databases