undefined | Better HN

0 pointsnikisweeting1mo ago0 comments

Having built production apps on SQLite I can say it's not all sunshine and roses, the complexity explodes the moment you need multiple workers that can all write.

You better hope you dont have any big indexes or your writes will queue and you start getting "database is locked" errors. Good luck queueing writes properly at the application layer without rebuilding a full distributed queue system / network interface / query retry system on top of SQLite.

I really really really wish SQLite or PGLite supported multiple writers, especially if the queries are not even touching the same tables.

0 comments

anonzzzies1mo ago

Oh I didn't say that, but nor is postgres. Use the right tool for the job I agree with, just people are making their lives difficult (expensive as well) by just blindly picking postgres.

j / k navigate · click thread line to collapse

0 pointsnikisweeting1mo ago0 comments

Having built production apps on SQLite I can say it's not all sunshine and roses, the complexity explodes the moment you need multiple workers that can all write.

I really really really wish SQLite or PGLite supported multiple writers, especially if the queries are not even touching the same tables.

0 comments

anonzzzies1mo ago

Oh I didn't say that, but nor is postgres. Use the right tool for the job I agree with, just people are making their lives difficult (expensive as well) by just blindly picking postgres.

j / k navigate · click thread line to collapse