4 ms·
Funny this article would pop up for me today, as I'm currently migrating my web app from sqlite to mysql. I got jazzed up on articles like this, only to figure
by frithsun 3y ago
Funny this article would pop up for me today, as I'm currently migrating my web app from sqlite to mysql.
I got jazzed up on articles like this, only to figure out the hard way that it's ill-suited to apps where concurrency matters.
Sqlite is an incredible piece of software, but it doesn't do scalable, concurrent things well.
- 0xbadcafebee 3y agoIt's almost as if reading trending blog posts isn't a great way to decide software architecture
- frithsun 3y agoI'm still soyfacing over sqlite and how elegant and powerful it is, and I'll continue deciding software architecture based on random blog posts. I have learned nothing.
- simonw 3y agoWere you using SQLite in WAL mode?
- frithsun 3y agoWAL Mode worked as advertised. But the project ended up being split into several autonomous workers, and even with WAL mode, sqlite gets problematic when you have several separate processes trying to read from and write to the same file.
- snovv_crash 3y agoConcurrent writes, no. Reads are fine though.