3 ms·
> use an inprocess database over https ie SQLite and Apache Why not, but you introduced a whole bunch of new issues. SQLite only supports a single writer at a
by ngrilly 10y ago
> use an inprocess database over https ie SQLite and Apache
Why not, but you introduced a whole bunch of new issues. SQLite only supports a single writer at a time. This is a problem if you have a lot of users on the same tenant. This is also a problem when you need to create an index, for example, which is not a background operation.
- marktangotango 10y agoIndeed there are trade offs, and high write applications are a weak spot of this approach. But for low to medium write applications (ie most applications?), SQLite WAL [1] option performs really well. We implement application level caching via a X-Query-Cache header[2], in that case, you're serving directly from redis. This set up can scale really, really well. [1] https://www.sqlite.org/wal.html https://www.sqlite.org/wal.html [2] https://www.lite-engine.com/docs.html#caching https://www.lite-engine.com/docs.html#caching