4 ms·
CMS would be low writes assuming no tracking or authentication audit trails or maybe buffered copies of all those.
by cosmotic 6y ago
CMS would be low writes assuming no tracking or authentication audit trails or maybe buffered copies of all those.
- slver 6y agoI wouldn't store web logs in an SQLite DB, but I wouldn't do that in any RDBMS typically. Easiest solution is a flat file, which you can import and analyze offsite (in SQLite, or Excel, or whatever :-).
- mrweasel 6y agoYou have a design where logs are added to a queue (something like ZMQ perhaps) and have a process/thread writing the logs to a separate SQLite database. I'm not saying it's a good idea, especially for logging, where a flat file might be better, but it is possible.
- slver 6y agoI was gonna say a queue, but I didn't want to get too fancy, but you're absolutely right. If you can use an in-memory/socket queue, even a basic one, which serializes the writes to a dedicated SQLite file, SQLite becomes as performant as any database (you're limited by disk I/O).