2 ms·
Why you should not use SQLite: Does not handle concurrent writers
by miohtama 3y ago
Why you should not use SQLite:
Does not handle concurrent writers
- starcraft2wol 3y agoThis doesn’t meant what you think it does. They lock and take turns. You can have hundreds of clients (on the same machine), and it works fine.
- simonw 3y agoIn practice I don't think this actually matters. SQLite can apply tens of thousands of small writes a second, so queueing them up works fine for all but the absolute largest scale applications.
- eatonphil 3y agoWithout too much difficulty you can get into the 100,000s inserts per second range, and even near 1M inserts per second. https://github.com/eatonphil/databases-intuition#go-mattngo-sqlite3-1 https://github.com/eatonphil/databases-intuition#go-mattngo-...
- astrostl 3y agoBetween its speed of operation and https://www.sqlite.org/src/doc/begin-concurrent/doc/begin_concurrent.md https://www.sqlite.org/src/doc/begin-concurrent/doc/begin_co... I'm not sure when or even if this becomes a functional limitation.