As far as I'm aware that threading information is on a per-connection basis. SQLite is perfectly capable of supporting multiple, parallel reads. SQLite must s

As far as I'm aware that threading information is on a per-connection basis. SQLite is perfectly capable of supporting multiple, parallel reads. SQLite must serialize writes, which makes a highly parallel write-heavy workload not good for it. However, with WAL enabled writes do not block reads. Basically highly-parallel read loads with low write counts (low-enough that serializing them doesn't lead to unacceptable slow down of writes) or with loads where latency is acceptable in writes (but not reads) is a perfect use case for SQLite. And it turns out that a lot of web services are heavily asymmetrically biased towards reads.