mylibsql
| Crates.io | mylibsql |
| lib.rs | mylibsql |
| version | 0.1.2 |
| created_at | 2025-02-03 16:32:39.193303+00 |
| updated_at | 2025-08-27 09:26:41.345792+00 |
| description | A personal take on libsql, enabling SQLite replication with application-controlled checkpointing—no dedicated server required |
| homepage | |
| repository | https://github.com/guillaumebort/mylibsql |
| max_upload_size | |
| id | 1540773 |
| size | 230,893 |
Guillaume Bort (guillaumebort)
documentation
https://docs.rs/mylibsql/latest/mylibsql/
README
mylibsql
mylibsql is a personal take on libsql, built for full control over SQLite replication—without a dedicated server. It uses libsql’s virtual WAL to support a primary-replica model where applications handle their own checkpointing and WAL log storage.
Why mylibsql?
- No server required – Replication is fully managed by the embedding application.
- Async durability – Writes only resolve when safely checkpointed.
- Checkpoint-based replication – WAL logs are durably stored and applied to replicas as needed.
- Built on libsql – Compatible with SQLite, leveraging libsql virtual WAL for replication.
How it works
- A Primary database is opened for reads and writes.
- Periodic Checkpoints generate WAL logs.
- These logs are stored durably (e.g., in an object store like S3).
- Replicas fetch and apply logs locally to stay in sync.
License
This project is licensed under the MIT License. See the LICENSE file for details.