Introducing LiteFS

1. fuse

   1 7 1,670 0.0 Go

   FUSE library for Go.  go get bazil.org/fuse   (by bazil)

   

   Yes, FUSE adds overhead. However,

   1. kernel page cache fully removes the read overhead for in-memory pages

   2. There's a FUSE_PASSTHROUGH mode that removes that overhead for all reads & writes. I haven't studied exactly what writes LiteFS needs to observe (just journal vs all data writes), but at least for reads it seems to pass them straight through. We could well submit a FUSE_PASSTHROUGH_READ patch to the kernel, and use that to remove all read overhead. The patch should be trivial, since the full FUSE_PASSTHROUGH mode is there already.

   Disclaimer: I wrote the FUSE framework LiteFS uses, https://bazil.org/fuse

   https://source.android.com/docs/core/storage/fuse-passthroug...

2. Stream

   getstream.io featured

   Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

   

3. litestream

   2 182 12,295 3.3 Go

   Streaming replication for SQLite.

   

   Thios is distributed SQLite 3, running (I assume at least partially managed?) Litestream[0] for you. Which is pretty cool!

   What I'd like to have seen is how this compares to things like rqlite[1] addressed directly in the article

   [0]: https://litestream.io/

4. litefs

   3 41 4,436 4.7 Go

   FUSE-based file system for replicating SQLite databases across a cluster of machines

   

   The TH3 test is proprietary and, IIRC, it might only be available to SQLite Consortium members and that's $125k/year. We do pay for SQLite support at Fly.io but not quite to that level.

   We do have plans to run against the Tcl test suite[1] although most of that test suite is not applicable to LiteFS since it tests higher level constructs.

   Since LiteFS acts on the raw pages, it really just functions similar to a VFS. Out of the 130K source lines of code in SQLite, only 4.8k are for the Unix VFS. As such, the testing coverage from the SQLite test suite mostly tests non-VFS code.

   [1]: https://github.com/superfly/litefs/issues/17

5. rqlite

   4 125 16,721 9.7 Go

   The lightweight, user-friendly, distributed relational database built on SQLite.

   

6. wunderbase

   5 12 523 10.0 Go

   Serverless GraphQL Database built on top of Firecracker, SQLite and Prisma

   

   Sound like a drop in solution to add high availability to WunderBase (https://github.com/wundergraph/wunderbase).

7. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

Suggest a related project