I use SQLite for everything, and I'm perfectly happy with it. I'm aware of the concurrent writer issues, but at my scale it doesn't even matter.

▲

zulux 39 minutes ago | parent | next [-]

Perfectly reasonable:

I'm a huge PG fan, so I start everything with it, but SQLite is sane, and it generally has a happy upgrade path to PG If you need it.

▲

thatwasunusual 31 minutes ago | parent [-]

It's the other way around for me: as 99% of the stuff I develop is .NET (and I use EF Core for database stuff), I can get away with SQLite for local development, prototyping (and even staging), and then just "flip a switch" for it to run on production PostgreSQL.

Both are amazing technologies.

	▲	bpavuk 22 minutes ago \| parent [-]
		EF Core is so easy to turn into a disgrace for performance, developer experience, AND build times...

▲

joewils an hour ago | parent | prev | next [-]

Same, I posted some corrections to Dr. Bauer's article: https://joecode.com/2026-08-19-sqlite3/

▲

bensyverson an hour ago | parent | prev | next [-]

Yes, especially for a web app where there’s realistically only a need for one VM/server. By the time you outgrow that approach, a very straightforward migration to Postgres is probably the least complex problem you face.

▲

Thaxll 26 minutes ago | parent | prev | next [-]

The main issue with SQLite is the very poor type system, after testing it for an app I was shocked.

	▲	OutOfHere a minute ago \| parent [-]
		Are you saying that STRICT was insufficient for you? What more did you want beyond one of: INT, INTEGER, REAL, TEXT, BLOB, ANY? https://sqlite.org/stricttables.html

▲

taoh an hour ago | parent | prev [-]

[dead]