this post was submitted on 26 Jun 2026
24 points (100.0% liked)
General Programming Discussion
9942 readers
11 users here now
A general programming discussion community.
Rules:
- Be civil.
- Please start discussions that spark conversation
Other communities
Systems
Functional Programming
Also related
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, it's amazing how good SQLite is nowadays. I find I use it for a lot of local apps I make for myself cause it's just good enough.
SQLite is pretty incredible. I think it currently has even faster read performance than postgres.
The only reason to not use it, is if you have a write-heavy DB, or you need some of postgres's extra features.
there have been some really neat projects using it too like this one https://github.com/biokoda/actordb
Or if you want too host it on NFS backed storage
That's my take as well, PostgreSQL is amazing, but in simpler DB schemes SQLite is undefeatable.
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.