3 ms·
sqlite is really only appropriate for things like mobile or desktop applications or things with generally low concurrency requirements. I think what you mean h
by contingencies 11y ago
sqlite is really only appropriate for things like mobile or desktop applications or things with generally low concurrency requirements.
I think what you mean here is low concurrent write requirements.
(Edit in response to below: Isn't sqlite file oriented and read-only opens eschew locking? Thus replication via network filesystems should be adequate, no?)
- spotman 11y agoYes, agreed, if we are talking about straight concurrency only. Other things like replication, are also not there, so it's not what I would choose for a website database, but if you can serve all your reads from one server, and don't care about high availability, then go for it.