> While technically, Synapse can work with a sqlite database (and which at first seems like an OK choice for having <10 users on the server), it WILL become corrupted.

Does anyone have any more information on this? Running Postgres is not a big deal, but I would expect SQLite to be fine given how well it works in my experience.

I've not seen many corrupted sqlite databases, but because Synapse is not currently storage-efficient you can end up with some terrifying large (100GB+) sqlite databases which might as well be corrupted.

We only ever supported sqlite for ease of tinkering; it was never intended to be used in production, and in retrospect supporting it at all was a mistake.

In terms of synapse storage efficiency and how to improve it, folks may be interested in https://www.youtube.com/watch?v=D5zAgVYBuGk&t=1851s

I use sqlite for my 2-user server and haven't had any issues in the several years I've been running it.

It's possible to corrupt a sqlite database file, but generally it shouldn't happen unless you're doing something weird with it. https://www.sqlite.org/howtocorrupt.html

I've been running unfederated Matrix instance with sqlite for 10 years for 10-20 people some very active. In WAL mode sqlite is fine i am not sure why it would get corrupted.

Few years ago we did a data/history wipe (i managed to migrate accounts) because we switched to conduit.rs with sqlite. I very much prefer conduit to synapse.

I never had issue with sqlite it was mostly Synapse. With recent changes i think they are completely dropping the ball on small instances and it feels like the ecosystem is splitting. Element X is just not very good. It seems to exist to kill classic element and since for element x you need some server features that not all alternative synapse servers support.