mvsqlite

I'm sad this project fizzled: https://github.com/losfair/mvsqlite It had the fascinating property of being a full multi-writer SQL engine when using Page Level Conflict Checking. Even more fascinating: every single client itself becomes a writer.

An abandoned project I'd love to see resurrected is SQLite on fdb: https://github.com/losfair/mvsqlite

My favorite FoundationDB layer is per-user SQLite databases: https://github.com/losfair/mvsqlite It's hard to tell if it's running in production, but the author works at Deno!

There's an intriguing project which puts SQLite on top of FoundationDB that is quite intriguing, unfortunately the dev seems to have moved on from that effort: https://github.com/losfair/mvsqlite

SQLite has the ability to do exactly this, minus the versioning: https://sqlite.org/cloudsqlite/doc/trunk/www/index.wiki Implementing snapshot backups on top of that would be as simple as a VACUUM and S3 PUT For point-in-time restores, mvsqlite is a cool solution: https://github.com/losfair/mvsqlite

Then maybe point of one of those databases: https://foundationdb.org/ https://tigerbeetle.com/ Or if you really wanna keep the SQLite theme: https://github.com/losfair/mvsqlite Why promote the vaporware project when comparing with something that's been in development for 10 years?

A small tangent on the subject of databases on top of FDB -- mvsqlite is such an insanely cool project and it looks like it's gone quiet. Any plans to pursue that further? For those that haven't seen it, SQLite on top of FoundationDB: https://github.com/losfair/mvsqlite

This sentiment has been repeated in a few comments. But, why can’t the deno deploy implementation be reimplemented, by yourself, by running a foundationDB server with mvSQLite[1]? That shouldn’t require any changes to the code. [1] https://github.com/losfair/mvsqlite

I’ve been using FDB for toy projects for a while. It’s truly rock solid. In my experience it’s the best open source database I’ve used, including mariadb, Postgres and cockroach. That being said, I wish there were more layers as the functionality out of the box is very very limited. Ideally someone could implement the firestore or dynamodb api on top. https://github.com/losfair/mvsqlite Is basically distributed SQLite backed by FDB. I’ve been scared to use it since I don’t know rust and can’t attest to if mvcc had been implemented correctly. In using this I actually realized how coupled the storage engine is to the storage system and how few open source projects make the storage engine easily swap-able.

Wild stuff - Fork of SQLite with new features https://github.com/libsql/libsql - And you can embed it in your application and it will really talk to your SQLite/libsql database over the network (subject of this blogpost): https://github.com/libsql/sqld - Oh, and if you're wondering about backup to S3, they have that too: https://github.com/libsql/bottomless - Uh, sqld can integrated with this https://github.com/losfair/mvsqlite, so now your SQLite is backed by FoundationDB!? -- - Meanwhile Litestream exists https://github.com/benbjohnson/litestream/ - Ben is developing https://github.com/superfly/litefs at Fly so that you can talk to your SQLite through a FUSE filesystem. (and work has stopped on the streaming replication effort https://github.com/benbjohnson/litestream/issues/8) - And, of course, SQLite has announced a new backend that h

> This was on HN a few months back: https://github.com/losfair/mvsqlite The lead developer on mvsqlite has since joined Deno...

This was on HN a few months back: https://github.com/losfair/mvsqlite While not Spanner, it is essentially an open source db like AlloyDB or Aurora, pushing replication and scale out to the storage layer (in this case via FoundationDB). The most interesting bit of mvsqlite is it's multi-writer capabilities, using FoundationDB to perform page-level locks. I'm neither the creator nor using it in production, but I'd love to see more DBs using FoundationDB as storage. It's a pretty cool solution.

Shameless plug of my mvSQLite [1] project here! It's basically another distributed SQLite (that is API-compatible with libsqlite3), but with support for everything expected from a proper distributed database: synchronous replication, strictly serializable transactions, + scalable reads and writes w/ multiple concurrent writers. [1] https://github.com/losfair/mvsqlite

This project looks really exciting! I'm working on mvsqlite [1], a distributed SQLite based on FoundationDB. When doing the VFS integration I have always wanted to patch SQLite itself, but didn't because of uncertainty around correctness of the patched version... A few features on my wishlist: 1. Asynchronous I/O. mvsqlite is currently doing its own prefetch prediction that is not very accurate. I assume higher layers in SQLite have more information that can help with better prediction. 2. Custom page allocator. SQLite internally uses a linked list to manage database pages - this causes contention on any two transactions that both allocate or free pages. 3. Random ROWID, without the `max(int64)` row trick. Sequentially increasing ROWIDs is a primary source of contention, and causes significant INSERT slowdown in my benchmark [2]. [1] http

The approach to edge-ifying SQLite taken in [1] looks quite promising - using FoundationDb as the storage handles a lot of hairiness. 1: https://github.com/losfair/mvsqlite