How does SQLite handle HA setups? The minimum I want is reliable automatic failover in reasonable time for user-facing service. Ideally an active-active setup.

▲ vhodges 3 hours ago | parent | next [-]

sqlite is just a library (in C)

A few projects:

  * https://github.com/rqlite/rqlite Distributed, fault tolerant cluster
  * https://litestream.io/ Replication to S3 (or compatible) - more disaster recovery than fail over
  * https://fly.io/docs/litefs/ Same Author as litestream).  Distributed replication.  Requires writes to be redirected to the primary.

I am debating Postgres vs sqlite (probably with litestream) for a project right now.

And other than HW redundancy, I can get pretty far by scaling vertically on a single box. And for my app, I could probably (and my users!) live with some occasional downtime (as long as the data is replicated/backed up).

If I get 20-50K users, it'll be a successful venture so I don't need much these days and it will be cheaper and easier to run as well.

	▲	otoolep 2 hours ago \| parent [-]
		rqlite creator here, happy to answer any questions.

▲ nchmy 2 hours ago | parent | prev [-]

there's various options now, but im most interested in Marmot - which is multi-master and just came out of a 2 year hibernation with a big overhaul that introduced a native gossip mechanism to replace NATS/Raft

https://github.com/maxpert/marmot/