Re:SQLite Is All You Need
by teaearlgraycold on Friday July 17, 2026 @07:15AM
(#48945893)
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.
[ Parent
| on HN ]
Article 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.
Re:SQLite Is All You Need
by callamdelaney on Friday July 17, 2026 @07:21AM
(#48945930)
Yeah 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.
WAL mode allows concurrency with reads and writes fwiw