A lot depends on your consistency requirements and data model here. I use SQLite heavily, and have evaluated litestream and rqlite but not deployed them, so be

A lot depends on your consistency requirements and data model here. I use SQLite heavily, and have evaluated litestream and rqlite but not deployed them, so bear that in mind. If the application is set up so that it serves a user for a session, so a given session ID is reading and writing from the same SQLite database, there are many opportunities to replicate that data optimistically, so that you won't lose it if a meteor hits the server, but it might not live in all the replicas right away, since applying patchsets off the gossip network happens in downtime. If concerns can't be isolated like this then yes, dedicated swarms of database servers are the way to go. Frequently they can be, and using SQLite punches way above its weight here.