3 ms·
For example you cannot have concurrent access. As soon as you need a worker process and a web process SQLite is out. Or if you are trying to use it as a vector
by teaearlgraycold 3mo ago
For example you cannot have concurrent access. As soon as you need a worker process and a web process SQLite is out. Or if you are trying to use it as a vector db all of those vector searches will block a node event loop.
- adzm 3mo agoWAL mode allows concurrency with reads and writes fwiw
- callamdelaney 3mo agoYeah it blocks for the 0.001ms it takes for 99.99% of queries to come back. Or you can enable WAL and allow readers to read at the same time as somebody is writing.
- smarx007 3mo agohttps://lobste.rs/s/ko1ji1/lobste_rs_is_now_running_on_sqlite https://lobste.rs/s/ko1ji1/lobste_rs_is_now_running_on_sqlit...
- chistev 3mo agoThat site is hard on my eyes
- Cthulhu_ 3mo agoArticle mentions WAL and how this sentiment is about 16 years out of date. But also, you can duplicate databases for out-of-order processes. But also also, if you have higher concurrency requirements - e.g. multiple servers, one database - or a more write-heavy use case, sqlite is no longer the right choice.