Example: single-writer-multiple-readers with Litestream + Minio about seafowl HOT 2 CLOSED

After some investigation, this doesn't seem to be worth it: Litestream doesn't do live replication (only backups/restores from S3). LiteFS does it, but requires FUSE + Consul (https://github.com/superfly/litefs). Maybe we'll get to revisit it when it's a native Fly platform offering.

We could maybe do a version of it where a read-only instance pulls the SQLite database in at startup, but then propagating changes would require a restart or some kind of a broadcast signal.

Archiving existing work at https://github.com/splitgraph/seafowl/tree/archive/litestream-sqlite-example.

from seafowl.

LiteFS now supports a single static reader: https://news.ycombinator.com/item?id=33206565, so this is possible without Consul. I've pushed some code for this to the archived branch, some things to finish:

• allow running SQLite catalog in a read-only mode (currently every node tries to run migrations)
• investigate a LiteFS issue with mismatched checksums on startup
• redraw the architecture diagram (we still need a volume to store the SQLite database, can't store it on Minio, but then replicas can copy the data from the leader instead of Minio anyway)
• actually try deploying this to Fly with support for the Fly-Replay header

from seafowl.