SQLite is not a single connection database
I think the most common misconception about SQLite which drives people away from that database is that it's a single connection database. This is not only confusing (what kind of connection is meant here?), but it's wrong in many aspects.
Read Operations
SQLite supports and works perfectly well with multiple concurrent reads. That's it.
Write Operations
The SQLite DB engine uses a write lock at the DB level, so only one "connection" can write at a time. Usually, this is not a problem because you can begin an IMMEDIATE TRANSACTION where SQLite will be able to queue this query to retry acquiring the write lock later.
Want to learn more about SQLite? Subscribe now!