News for hackers. Stuff that matters.
Re:The Winamp Skin Museum is powered by a SQLite3 database w... by manigandham on Saturday June 11, 2022 @07:38PM (#31709569)
SQLite WAL mode means readers and writer don't block each other: https://www.sqlite.org/wal.html

Since it's SQLite, it's also trivial to just copy the database file as a snapshot for separate OLAP queries if necessary.

Re:The Winamp Skin Museum is powered by a SQLite3 database w... by derefr on Sunday June 12, 2022 @02:19PM (#31716860)
Not all OLAP queries are for reporting. Sometimes they drive OLTP processes — really complex, separate-statements but same-transaction equivalents to "INSERT/UPDATE/DELETE ... WHERE" queries.

Of course, you can still drive those using a separate snapshot for the read side, to generate an ID set for a follow-up write on the business layer. But now you're doing CQRS — less trivial. You're not getting any of the ACID benefits of doing the OLAP and OLTP queries together in a single transaction; so your data model has to be designed for that (by e.g. having all tables be temporal tables.)