we have more performance issues developing gotosocial with postgres than with sqlite. if we supported multinode deployments or horizontal scaling such that sqlite's concurrency got harder to reason-about I'm sure postgres would shine, but for a single process sqlite has been generally much faster and it hasn't required anywhere near as much prompting to get the query planner to behave as required.

i also think when people assume sqlite is better for simpler applications, they think smaller. but no, for the same 25+GB databases sqlite has mopped the floor with performance.

single-process multi-threaded sqlite is fantastic.