SQLite-based databases on the Postgres protocol
Wild stuff<p>- Fork of SQLite with new features <a href="https://github.com/libsql/libsql">https://github.com/libsql/libsql</a><p>- 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): <a href="https://github.com/libsql/sqld">https://github.com/libsql/sqld</a><p>- Oh, and if you're wondering about backup to S3, they have that too: <a href="https://github.com/libsql/bottomless">https://github.com/libsql/bottomless</a><p>- Uh, sqld can integrated with this <a href="https://github.com/losfair/mvsqlite">https://github.com/losfair/mvsqlite</a>, so now your SQLite is backed by FoundationDB!?<p>--<p>- Meanwhile Litestream exists <a href="https://github.com/benbjohnson/litestream/">https://github.com/benbjohnson/litestream/</a><p>- Ben is developing <a href="https://github.com/superfly/litefs">https://github.com/superfly/litefs</a> at Fly so that you can talk to your SQLite through a FUSE filesystem. (and work has stopped on the streaming replication effort <a href="https://github.com/benbjohnson/litestream/issues/8">https://github.com/benbjohnson/litestream/issues/8</a>)<p>- And, of course, SQLite has announced a new backend that hopes to support concurrent writes and streaming replication: <a href="https://sqlite.org/hctree/doc/hctree/doc/hctree/index.html" rel="nofollow">https://sqlite.org/hctree/doc/hctree/doc/hctree/index.html</a><p>What a time for SQLite<p>Presumably all of these things provide a wildly different experience in terms of consistency, availability, latency, complexity, and concurrent use. Would be so nice to read a lengthy blogpost comparing all or some of these with their pros and cons.