A standalone component of the vlcn project | discord.
crsql is a run time loadable extension for SQLite that adds CRDT and sync support.
SQLite is a foundation of offline, local-first and edge deployed software. Wouldn't it be great, however, if we could merge two or more SQLite databases together and not run into any conflicts?
This project implements CRDTs and CRRs in SQLite, allowing databases that share a common schema to merge their state together. Merges can happen between an arbitrary number of peers and all peers will eventually converge to the same state.
crsqlite works by adding metadata tables and triggers around your existing database schema. This means that you do not have to change your schema in order to get conflict resolution support -- with a few caveats around uniqueness constraints and foreign keys. See Schema Design for CRDTs & Eventual Consistency.
ReflectThe full documentation site is available here.
crsqlite exposes three APIs:
- A function extension (
crsql_as_crr) to upgrade existing tables to "crrs" or "conflict free replicated relations"SELECT crsql_as_crr('table_name')
- A virtual table (
crsql_changes) to ask the database for changesets or to apply changesets from another databaseSELECT * FROM crsql_changes WHERE db_version > x AND site_id IS NULL-- to get local changesSELECT * FROM crsql_changes WHERE db_version > x AND site_id != some_site-- to get all changes excluding those synced from some siteINSERT INTO crsql_changes VALUES ([patches receied from select on another peer])
- And (on latest)
crsql_alter_begin('table_name')&crsql_alter_commit('table_name')primitives to allow altering table definitions that have been upgraded tocrrs.- Until we move forward with extending the syntax of SQLite to be CRR aware, altering CRRs looks like:
A future version of cr-sqlite may extend the SQL syntax to make this more natural.
SELECT crsql_alter_begin('table_name'); -- 1 or more alterations to `table_name` ALTER TABLE table_name ...; SELECT crsql_alter_commit('table_name');
- Until we move forward with extending the syntax of SQLite to be CRR aware, altering CRRs looks like:
Application code would use the function extension to enable crr support on tables.
Networking code would use the crsql_changes virtual table to fetch and apply changes.
Usage looks like:
-- load the extension if it is not statically linked
.load crsqlite
.mode column
-- create tables as normal
create table foo (a primary key, b);
create table baz (a primary key, b, c, d);
-- update those tables to be crrs / crdts
select crsql_as_crr('foo');
select crsql_as_crr('baz');
-- insert some data / interact with tables as normal
insert into foo (a,b) values (1,2);
insert into baz (a,b,c,d) values ('a', 'woo', 'doo', 'daa');
-- ask for a record of what has changed
select * from crsql_changes;
table pk cid val col_version db_version site_id
----- --- --- ----- ----------- ---------- -------
foo 1 b 2 1 1 1(�zL
\hx
baz 'a' b 'woo' 1 2 1(�zL
\hx
baz 'a' c 'doo' 1 2 1(�zL
\hx
baz 'a' d 'daa' 1 2 1(�zL
\hx
-- merge changes from a peer
insert into crsql_changes
("table", pk, cid, val, col_version, db_version, site_id)
values
('foo', 5, 'b', '''thing''', 5, 5, X'7096E2D505314699A59C95FABA14ABB5');
insert into crsql_changes ("table", pk, cid, val, col_version, db_version, site_id)
values
('baz', '''a''', 'b', 123, 101, 233, X'7096E2D505314699A59C95FABA14ABB5');
-- check that peer's changes were applied
select * from foo;
a b
- -----
1 2
5 thing
select * from baz;
a b c d
- --- --- ---
a 123 doo daa
-- tear down the extension before closing the connection
-- https://sqlite.org/forum/forumpost/c94f943821
select crsql_finalize();Pre-built binaries of the extension are available in the releases section.
These can be loaded into sqlite via the load_extension command from any language (Python, NodeJS, C++, Rust, etc.) that has SQLite bindings.
The entrypoint to the loadable extension is sqlite3_crsqlite_init so you'll either need to provide that to load_extension or rename your binary to crsqlite.[dylib/dll/so]. See the linked sqlite load_extension docs.
Note: if you're using
cr-sqliteas a run time loadable extension, loading the extension should be the first operation you do after opening a connection to the database. The extension needs to be loaded on every connection you create.
For a WASM build that works in the browser, see the js directory.
For UI integrations (e.g., React) see the [js]./js) directory.
Examples apps that use cr-sqlite and have a networking layer:
Until we have a nix flake, you'll need to install Rust and the nightly toolchain.
- Installing Rust: https://www.rust-lang.org/tools/install
- Adding the nightly toolchain:
rustup toolchain install nightly
If you're building on windows: rustup toolchain install nightly-x86_64-pc-windows-gnu
Instructions on building a native library that can be loaded into SQLite in non-wasm environments.
rustup toolchain install nightly # make sure you have the rust nightly toolchain
git clone --recurse-submodules [email protected]:vlcn-io/cr-sqlite.git
cd cr-sqlite/core
make loadableThis will create a shared library at dist/crsqlite.[lib extension]
[lib extension]:
- Linux:
.so - Darwin / OS X:
.dylib - Windows:
.dll
Instructions on building a sqlite3 CLI that has cr-sqlite statically linked and pre-loaded.
In the core directory of the project, run:
make sqlite3This will create a sqlite3 binary at dist/sqlite3
Ensure you've installed depenencies via pnpm isntall in the root director then run:
pnpm testThis will run all tests across native, js & python packages.
pnpm, not npm.
For a WASM build that works in the browser, see the js directory.
JS APIs for using cr-sqlite in the browser are not yet documented but exist in the js dir. You can also see examples of them in use here:
https://munin.uit.no/bitstream/handle/10037/22344/thesis.pdf?sequence=2
crsqlite improves upon [1] in the following ways --
- [1] stores two copies of all the data.
crsqliteonly keeps one by leveraging views andISNTEAD OFtriggers. - [1] cannot compute deltas between databases without sending the full copy of each database to be compared.
crsqliteonly needs the logical clock (1 64bit int per peer) of a given database to determine what updates that database is missing.
https://hal.inria.fr/hal-02983557/document
crsqlite improves upon [2] in the following ways --
- [2] is implemented in a specific ORM.
crsqliteruns at the db layer and allows existing applications to interface with the db as normal. - [2] keeps a queue of all writes. This queue is drained when those writes are merged. This means that [2] can only sync changes to a single centralized node.
crsqlitekeeps a logical clock at each database. If a new database comes online it sends its logical clock to a peer. That peer can compute what changes are missing from the clock.
https://www.youtube.com/watch?v=DEcwa68f-jY
crsqlite improves upon [3] in the following ways --
- [3] requires retaining all history for all time (iiuc),
crsqliteonly needs the latest state - [3] keeps a hloc per column,
crsqliteonly keeps an extra int per column and a clock per row.
[3] is better in the following way --
crsqliterequires more work at the network layer to ensure ordered delivery and to deliver only the columns of a row that changed. [3] doesn't require any causal order to delivery and already identifies single column changes.
These projects helped improve my understanding of CRDTs on this journey --
crsqlite currently does not support:
- Foreign key cosntraints. You can still have foreign keys (i.e. a column with an id of another row), but they can't be enforced by the db.
- Enforced foreign key constraints will eventually be supported as we enable more deletion strategies. There are 4 deletion models under which CRDT updates do not break foreign key constraints.
- Uniqueness constraints other than the primary key. The only enforceably unique column in a table should be the primary key. Other columns may be indices but they may not be unique.
Tables are modeled as GSets where each item has a causal length. You can call this a "CLSet". This allows us to keep all rows as well as track deletes so your application will not see deleted rows.
Rows are currently modeled as LWW maps. I.e., each column in a row is a LWW Register.
Things to support in the future
- counter columns
- MVR (multi-value register) columns
Deltas between databases are calculated by each database keeping a version vector that represents the last time it synced with a given peer.
Every row and column in the database is associated with a lamport timestamp. This clock allows peers to ask one another for updates since the last time they communicated.
- Sharing & Privacy -- in a real-world collaborative scenario, you may not want to share your entire database with other peers. Thus, in addition to clock information, we must keep visibility information to use when computing deltas and doing replication.
- Query based replication -- peers may want to sync subsets of the database even if they have access to the entire thing. Compute deltas but only send those deltas that fall into the peer's provided query.
Say we have a database schema called "Animal App." Alice, Bob and Billy all have local copies of "Animal App" on their devices. They start their day at a hostel with all of their devices synced. They then part ways, backpacking into the wilderness each with their own copy of the db.
As they see different (or maybe even the same) animals, they record their observations.
- Name
- Genus
- Species
- Habitat
- Diet
- Etc.
Some observations may even involve making updates to the prior day's (or week's) observations written by other members of the party.
At the end of the day, the group comes back together. They need to merge all of their work. crsqlite will allow Alice, Bob and Billy to merge their changes (without conflict) in a p2p fashion and converge to the same state.
Note that "without conflict" would be based on the rules of the selected CRDTs used within the schema.
Some example are --
- Tables might be grow only sets -- thus never losing an observation.
- Or sets with a causal length so we can safely remove rows
- Table columns might be last write win (LWW) registers -- converging but throwing out earlier writes
- Table columns might be multi value (MV) registers -- keeping around all concurrent edits to a single column for users (or code) to pick and merge later.
- A column might be a counter CRDT which accumulates all observations from all parties
A description of the original design. Note that this design was only used for the prototype and we've evolved it for the production version --
